Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4b82be05b0a08f328101cd0dfb66bce5f58628b90295d76c693877a90444fba

Tx prefix hash: a70f59db59a55b7e1f98f23d95ec3f21ed8bdee7c31f1fab6b75e711c1a38392
Tx public key: 5efeddab23f8023cdfb85b48d80143331273c248e871628d1074d196f890a435
Timestamp: 1720588800 Timestamp [UCT]: 2024-07-10 05:20:00 Age [y:d:h:m:s]: 00:310:18:13:51
Block: 1062437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222056 RingCT/type: yes/0
Extra: 015efeddab23f8023cdfb85b48d80143331273c248e871628d1074d196f890a43502110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 418dda21b6f48e50b073c2f76a4a8b331fd3c2353e95c2cf26b343167a5e6aa6 0.600000000000 1532940 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": 1062447, "vin": [ { "gen": { "height": 1062437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "418dda21b6f48e50b073c2f76a4a8b331fd3c2353e95c2cf26b343167a5e6aa6" } } ], "extra": [ 1, 94, 254, 221, 171, 35, 248, 2, 60, 223, 184, 91, 72, 216, 1, 67, 51, 18, 115, 194, 72, 232, 113, 98, 141, 16, 116, 209, 150, 248, 144, 164, 53, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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