Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd15a83559d727039bf1ea27ec9d55e7ba2788de4fea24795aea93eead73eaaf

Tx prefix hash: 82dc178d15e55b34e5cfa8a473d12530a598acb3d1fc757b6741676100d4c581
Tx public key: d000ceb62a8e92caa390181903adf72ed6a69a118ebfc80937a51ae45806a336
Timestamp: 1706445930 Timestamp [UCT]: 2024-01-28 12:45:30 Age [y:d:h:m:s]: 01:284:21:09:41
Block: 945158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462418 RingCT/type: yes/0
Extra: 01d000ceb62a8e92caa390181903adf72ed6a69a118ebfc80937a51ae45806a33602110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e31a47f7e53be2debb8f3a66cc0fb564cc3d49b1e0f7d20379ad748b7d52fbfc 0.600000000000 1403468 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": 945168, "vin": [ { "gen": { "height": 945158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e31a47f7e53be2debb8f3a66cc0fb564cc3d49b1e0f7d20379ad748b7d52fbfc" } } ], "extra": [ 1, 208, 0, 206, 182, 42, 142, 146, 202, 163, 144, 24, 25, 3, 173, 247, 46, 214, 166, 154, 17, 142, 191, 200, 9, 55, 165, 26, 228, 88, 6, 163, 54, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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