Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e0f623c9f8aad4dc9a9417cec2002598a8316473233e0d1215468103445b23d

Tx prefix hash: 87734e49d4e01e11faca5d166e4cae4ccc08cc28dccfeb5c5399a63ff9905ec1
Tx public key: bd500235f0ea8a20ab2ba92bb7c19bc7a32b52ded1e3aa521d151a23e8e46e33
Timestamp: 1713074433 Timestamp [UCT]: 2024-04-14 06:00:33 Age [y:d:h:m:s]: 01:020:21:19:44
Block: 1000120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275899 RingCT/type: yes/0
Extra: 01bd500235f0ea8a20ab2ba92bb7c19bc7a32b52ded1e3aa521d151a23e8e46e330211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77353593e237b165c2c9650d86c747746ed3d386808a4c5b85fba7be9e8aa208 0.600000000000 1460612 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": 1000130, "vin": [ { "gen": { "height": 1000120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77353593e237b165c2c9650d86c747746ed3d386808a4c5b85fba7be9e8aa208" } } ], "extra": [ 1, 189, 80, 2, 53, 240, 234, 138, 32, 171, 43, 169, 43, 183, 193, 155, 199, 163, 43, 82, 222, 209, 227, 170, 82, 29, 21, 26, 35, 232, 228, 110, 51, 2, 17, 0, 0, 0, 1, 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