Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6625c1e6964e2db653228de35824f328d21ea23692daeb04fadf51e0591cbf6

Tx prefix hash: ae6d16bc40d26414daad5d45429e53fdf24eecbc116417e2983abcb9210b4849
Tx public key: 37f6dd5c2256251fba6b33ad43277d1c94d05fd1186e68f845d05aa8248f4113
Timestamp: 1720863181 Timestamp [UCT]: 2024-07-13 09:33:01 Age [y:d:h:m:s]: 00:245:05:24:33
Block: 1064728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175189 RingCT/type: yes/0
Extra: 0137f6dd5c2256251fba6b33ad43277d1c94d05fd1186e68f845d05aa8248f411302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c7ed68147419970ccb0e47f162b0daa3d803170d8700b35d0a0365addf607d9 0.600000000000 1535263 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": 1064738, "vin": [ { "gen": { "height": 1064728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c7ed68147419970ccb0e47f162b0daa3d803170d8700b35d0a0365addf607d9" } } ], "extra": [ 1, 55, 246, 221, 92, 34, 86, 37, 31, 186, 107, 51, 173, 67, 39, 125, 28, 148, 208, 95, 209, 24, 110, 104, 248, 69, 208, 90, 168, 36, 143, 65, 19, 2, 17, 0, 0, 0, 2, 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