Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6e5ca33611609ff4cddf9dbf08ea5bba29602a60e58aecb36228f1f01dbc9a6

Tx prefix hash: e5ac731ad779c2d1503eea790df53e7c16c5c5114dc130ea77543f4a38216294
Tx public key: aa25e05d03be9275534151adac5a48acee8bf26e5427c0220e22b098be696b5e
Timestamp: 1717544412 Timestamp [UCT]: 2024-06-04 23:40:12 Age [y:d:h:m:s]: 00:302:20:19:30
Block: 1037202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216419 RingCT/type: yes/0
Extra: 01aa25e05d03be9275534151adac5a48acee8bf26e5427c0220e22b098be696b5e02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32fc7d51daa0c357ce9d62ffb5c243c327a4fb9e8433b6fd2abf334be3f6954e 0.600000000000 1505733 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": 1037212, "vin": [ { "gen": { "height": 1037202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32fc7d51daa0c357ce9d62ffb5c243c327a4fb9e8433b6fd2abf334be3f6954e" } } ], "extra": [ 1, 170, 37, 224, 93, 3, 190, 146, 117, 83, 65, 81, 173, 172, 90, 72, 172, 238, 139, 242, 110, 84, 39, 192, 34, 14, 34, 176, 152, 190, 105, 107, 94, 2, 17, 0, 0, 0, 5, 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