Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fd7dd89a86d03e4a6b1b1292219381168fae1212faa501f1174dc26b71ee6a8

Tx prefix hash: 509abce7c7c16017abe2de55b3c2a1bbd1b038f12f370a07689976d56530c2d6
Tx public key: 79b40595418bb62919525fe9e3608a9de3c9b2d85ad78486b527339465fd6ea3
Timestamp: 1706262788 Timestamp [UCT]: 2024-01-26 09:53:08 Age [y:d:h:m:s]: 01:094:19:37:27
Block: 943635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328879 RingCT/type: yes/0
Extra: 0179b40595418bb62919525fe9e3608a9de3c9b2d85ad78486b527339465fd6ea30211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdb33f35341646e3d8df546c761ce899ab8520e7fd8ee402b0e3a8fa76bac5a0 0.600000000000 1401843 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": 943645, "vin": [ { "gen": { "height": 943635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdb33f35341646e3d8df546c761ce899ab8520e7fd8ee402b0e3a8fa76bac5a0" } } ], "extra": [ 1, 121, 180, 5, 149, 65, 139, 182, 41, 25, 82, 95, 233, 227, 96, 138, 157, 227, 201, 178, 216, 90, 215, 132, 134, 181, 39, 51, 148, 101, 253, 110, 163, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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