Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55e6d360dc010ba432f93cfe8b117315a367fd157f8bf49267e05d9ff1ab63af

Tx prefix hash: 1810b18d9e9ac26584e8e6845051fde05bed77039a5d7c526f76c28ee29b57db
Tx public key: 3c8b975874915a7ed4836b7dfdc7b7ba5451ec3a30256c2e952c56ae658e4bb1
Timestamp: 1721347342 Timestamp [UCT]: 2024-07-19 00:02:22 Age [y:d:h:m:s]: 00:258:21:03:46
Block: 1068739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184919 RingCT/type: yes/0
Extra: 013c8b975874915a7ed4836b7dfdc7b7ba5451ec3a30256c2e952c56ae658e4bb1021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2af16caba020e910ef81f60ec4703532991f3db52ef41fd403fbab5f1aebb9f5 0.600000000000 1539888 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": 1068749, "vin": [ { "gen": { "height": 1068739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2af16caba020e910ef81f60ec4703532991f3db52ef41fd403fbab5f1aebb9f5" } } ], "extra": [ 1, 60, 139, 151, 88, 116, 145, 90, 126, 212, 131, 107, 125, 253, 199, 183, 186, 84, 81, 236, 58, 48, 37, 108, 46, 149, 44, 86, 174, 101, 142, 75, 177, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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