Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d61e8018e8536a1db1e828050bf9dc66ab7e3a95fe1489011f7c3ddce72526b

Tx prefix hash: 24ea8609716b3e53decb09048277d4456ffa906661f4ed60d33f881190ac201f
Tx public key: b2947df86a0be7cd5cd14bf9c88d47c573b6960d7c6b7500b369b143948a59b3
Timestamp: 1710239066 Timestamp [UCT]: 2024-03-12 10:24:26 Age [y:d:h:m:s]: 00:348:06:45:24
Block: 976646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248989 RingCT/type: yes/0
Extra: 01b2947df86a0be7cd5cd14bf9c88d47c573b6960d7c6b7500b369b143948a59b302110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa721983b37c356c9c1fd9f70a09dff3018c3bba2f9afec8bb2c1f25934aefb7 0.600000000000 1436641 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": 976656, "vin": [ { "gen": { "height": 976646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa721983b37c356c9c1fd9f70a09dff3018c3bba2f9afec8bb2c1f25934aefb7" } } ], "extra": [ 1, 178, 148, 125, 248, 106, 11, 231, 205, 92, 209, 75, 249, 200, 141, 71, 197, 115, 182, 150, 13, 124, 107, 117, 0, 179, 105, 177, 67, 148, 138, 89, 179, 2, 17, 0, 0, 0, 7, 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