Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3c1631524ac4d3cb8c87f5a57601d4afde72bc39fb4f6a32fa6be4de7d2bef7

Tx prefix hash: cd48e5eda431299cb32d6bd2812a66d1626a68ae2587e422635a89da58ba7f0e
Tx public key: b12ae1701d304817d50c094329a329cb3117a068b23bbbc073f2e7143ef9b0ac
Timestamp: 1583639643 Timestamp [UCT]: 2020-03-08 03:54:03 Age [y:d:h:m:s]: 05:242:02:00:32
Block: 78515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1326072 RingCT/type: yes/0
Extra: 01b12ae1701d304817d50c094329a329cb3117a068b23bbbc073f2e7143ef9b0ac0211000000215143fba2000000000000000000

1 output(s) for total of 337.169284242000 dcy

stealth address amount amount idx
00: 2004e8c935f189ea6818b16238bf901fe8b8c57d41bbb7e2c2f767b581f05251 337.169284242000 143975 of 0

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": 78525, "vin": [ { "gen": { "height": 78515 } } ], "vout": [ { "amount": 337169284242, "target": { "key": "2004e8c935f189ea6818b16238bf901fe8b8c57d41bbb7e2c2f767b581f05251" } } ], "extra": [ 1, 177, 42, 225, 112, 29, 48, 72, 23, 213, 12, 9, 67, 41, 163, 41, 203, 49, 23, 160, 104, 178, 59, 187, 192, 115, 242, 231, 20, 62, 249, 176, 172, 2, 17, 0, 0, 0, 33, 81, 67, 251, 162, 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