Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 516e45fb2add056a048209d0d59f8fc455a725614cbf0412c1822409970f9dd4

Tx prefix hash: 0e58bf8f635726bdfd448a30fe5c8529f1b3aeb3b0c9adeea9db6a1c9f59695e
Tx public key: 88e0f837326fcf372411a4b0effd05158c4cc5745bb1fbc1446bb09e6bbd69cb
Timestamp: 1685567374 Timestamp [UCT]: 2023-05-31 21:09:34 Age [y:d:h:m:s]: 01:226:12:12:49
Block: 772340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423306 RingCT/type: yes/0
Extra: 0188e0f837326fcf372411a4b0effd05158c4cc5745bb1fbc1446bb09e6bbd69cb0211000000014b8f5122000000000000000000

1 output(s) for total of 1.694294552000 dcy

stealth address amount amount idx
00: e4ae6f45a8d353e3771e9163e2de8ea2b7cf660f5f14cf37dbc338b29d36482a 1.694294552000 1221737 of 0

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": 772350, "vin": [ { "gen": { "height": 772340 } } ], "vout": [ { "amount": 1694294552, "target": { "key": "e4ae6f45a8d353e3771e9163e2de8ea2b7cf660f5f14cf37dbc338b29d36482a" } } ], "extra": [ 1, 136, 224, 248, 55, 50, 111, 207, 55, 36, 17, 164, 176, 239, 253, 5, 21, 140, 76, 197, 116, 91, 177, 251, 193, 68, 107, 176, 158, 107, 189, 105, 203, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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