Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c899b98e8bfe4164fa0d895eb5acf6b144e59103194dea273b6b0a1efed35c7e

Tx prefix hash: 878e06f54a8117844d8f1b227f5d11d67362ad56cb50722ccc264830cedaea44
Tx public key: e38b2b225f16e1c3d8d1ca96eb20d2de58ee2db29dcd4efa920e195e75f0d559
Timestamp: 1740996831 Timestamp [UCT]: 2025-03-03 10:13:51 Age [y:d:h:m:s]: 00:256:00:32:31
Block: 1231164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180729 RingCT/type: yes/0
Extra: 01e38b2b225f16e1c3d8d1ca96eb20d2de58ee2db29dcd4efa920e195e75f0d5590211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4eb89b9c94ed87486749b904b47bf80bc4c4cc2597204d8110bb160c16a38903 0.600000000000 1718069 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": 1231174, "vin": [ { "gen": { "height": 1231164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4eb89b9c94ed87486749b904b47bf80bc4c4cc2597204d8110bb160c16a38903" } } ], "extra": [ 1, 227, 139, 43, 34, 95, 22, 225, 195, 216, 209, 202, 150, 235, 32, 210, 222, 88, 238, 45, 178, 157, 205, 78, 250, 146, 14, 25, 94, 117, 240, 213, 89, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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