Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00e96345f4cda2ae64e91fd917b256c3843f78b9bb61c864eb30416792fe2874

Tx prefix hash: a71ee890fe61545a2e97141c9cfea4f2513711550a029ecf0f7cb4137a93a3b5
Tx public key: 1bbd6ca4153119224bd30fb78ec239a1109c85acb40cb2f9c952f2e0c3907d9f
Timestamp: 1741292282 Timestamp [UCT]: 2025-03-06 20:18:02 Age [y:d:h:m:s]: 00:005:21:12:36
Block: 1233612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4224 RingCT/type: yes/0
Extra: 011bbd6ca4153119224bd30fb78ec239a1109c85acb40cb2f9c952f2e0c3907d9f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0f1fd03407387e79a94b32af749014b90859377dd9a2a6a14f34d1e20c9bf8e 0.600000000000 1720535 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": 1233622, "vin": [ { "gen": { "height": 1233612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0f1fd03407387e79a94b32af749014b90859377dd9a2a6a14f34d1e20c9bf8e" } } ], "extra": [ 1, 27, 189, 108, 164, 21, 49, 25, 34, 75, 211, 15, 183, 142, 194, 57, 161, 16, 156, 133, 172, 180, 12, 178, 249, 201, 82, 242, 224, 195, 144, 125, 159, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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