Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf2d06c9dba7a64035c8528212312d43d368ad748abaed41b57fc6efa43c3274

Tx prefix hash: 39de4e309a20a08bfbc49e2d4c89a262f5939c2125ddd09657c5e3ba7268aae3
Tx public key: 93df3d917eaf00f6df0b76df7b1e0093c150b4d5975c19d8860fae3f3f1d0ea7
Timestamp: 1724858569 Timestamp [UCT]: 2024-08-28 15:22:49 Age [y:d:h:m:s]: 00:224:02:08:37
Block: 1097834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160014 RingCT/type: yes/0
Extra: 0193df3d917eaf00f6df0b76df7b1e0093c150b4d5975c19d8860fae3f3f1d0ea702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd99d43e6c6215df0ef593f68176ccd278431dbcdbec945a7fc050dd85d54ca2 0.600000000000 1573337 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": 1097844, "vin": [ { "gen": { "height": 1097834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd99d43e6c6215df0ef593f68176ccd278431dbcdbec945a7fc050dd85d54ca2" } } ], "extra": [ 1, 147, 223, 61, 145, 126, 175, 0, 246, 223, 11, 118, 223, 123, 30, 0, 147, 193, 80, 180, 213, 151, 92, 25, 216, 134, 15, 174, 63, 63, 29, 14, 167, 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