Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84890dcbc3a8e8c3ae6132fe2ff3704f1bf2798c183fa0219762a09857465c26

Tx prefix hash: 5b2d938d22ed637581f94d7a284cb816949dc130958cb4de47b1028a663ad22e
Tx public key: e1d1c16f4d89fa9eee0b74e06cba94d52a9e8b93c287b240a33f3a0c6f144289
Timestamp: 1721927493 Timestamp [UCT]: 2024-07-25 17:11:33 Age [y:d:h:m:s]: 00:242:00:30:56
Block: 1073531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172879 RingCT/type: yes/0
Extra: 01e1d1c16f4d89fa9eee0b74e06cba94d52a9e8b93c287b240a33f3a0c6f144289021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e37550be231f85e6c372528619ecdcea2d4e6bc3693449bf22ad7400be0df27 0.600000000000 1546034 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": 1073541, "vin": [ { "gen": { "height": 1073531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e37550be231f85e6c372528619ecdcea2d4e6bc3693449bf22ad7400be0df27" } } ], "extra": [ 1, 225, 209, 193, 111, 77, 137, 250, 158, 238, 11, 116, 224, 108, 186, 148, 213, 42, 158, 139, 147, 194, 135, 178, 64, 163, 63, 58, 12, 111, 20, 66, 137, 2, 17, 0, 0, 0, 8, 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