Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 10e6c1168e866e4ae59b93a1f0b650de82d0169a9ad8e45c718ceadae338389c

Tx prefix hash: d2e367cd17bf0bb7c5c0cbc546a685e854fbf12981f97ea9379d211f976b5d4f
Tx public key: f8cd8a06f45cb01cbb081a5afc770344346b554a33674e90880dbe8554d713c9
Timestamp: 1707521468 Timestamp [UCT]: 2024-02-09 23:31:08 Age [y:d:h:m:s]: 01:279:21:21:08
Block: 954091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458818 RingCT/type: yes/0
Extra: 01f8cd8a06f45cb01cbb081a5afc770344346b554a33674e90880dbe8554d713c90211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0add26057deacf206275990388c5a80ac83c3e04ed84ab31582bd3f58b54888 0.600000000000 1413365 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 954101, "vin": [ { "gen": { "height": 954091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0add26057deacf206275990388c5a80ac83c3e04ed84ab31582bd3f58b54888" } } ], "extra": [ 1, 248, 205, 138, 6, 244, 92, 176, 28, 187, 8, 26, 90, 252, 119, 3, 68, 52, 107, 85, 74, 51, 103, 78, 144, 136, 13, 190, 133, 84, 215, 19, 201, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8