Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ef04b9e836cb89540450152f77fd78e0515ac4c76e81fd910d50963cd6699b6

Tx prefix hash: 5cb3992379c97347db6cb087334a4a2a664bc40c32d47425f59fd14dd78a9ed7
Tx public key: 031b2df8a05636442a0f1d40f56f1fb0e60969ca6ba33ea623a83ee7198d7a5a
Timestamp: 1700998581 Timestamp [UCT]: 2023-11-26 11:36:21 Age [y:d:h:m:s]: 01:200:12:53:56
Block: 900018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404463 RingCT/type: yes/0
Extra: 01031b2df8a05636442a0f1d40f56f1fb0e60969ca6ba33ea623a83ee7198d7a5a0211000000014b8f5122000000000000000000

1 output(s) for total of 0.639538559000 dcy

stealth address amount amount idx
00: e27def62098962c8c23125fc6c0ccd28ea6d5f6c9884967a7a9abb4f39b75858 0.639538559000 1356493 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": 900028, "vin": [ { "gen": { "height": 900018 } } ], "vout": [ { "amount": 639538559, "target": { "key": "e27def62098962c8c23125fc6c0ccd28ea6d5f6c9884967a7a9abb4f39b75858" } } ], "extra": [ 1, 3, 27, 45, 248, 160, 86, 54, 68, 42, 15, 29, 64, 245, 111, 31, 176, 230, 9, 105, 202, 107, 163, 62, 166, 35, 168, 62, 231, 25, 141, 122, 90, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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