Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e79da0430bcf0e0906f5ae16de3822fb1d22af41b59eda99164a4c4ed7901b4

Tx prefix hash: b675f62817ac80fa8233ef2a3998d4530265fd5236df5092e553e4723bd8a291
Tx public key: fc7e5b67d93a4fc6a241b6df05fee901ce31a3a51091df1a2a98f053bf7ab3d3
Timestamp: 1708890734 Timestamp [UCT]: 2024-02-25 19:52:14 Age [y:d:h:m:s]: 01:283:04:14:24
Block: 965460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461160 RingCT/type: yes/0
Extra: 01fc7e5b67d93a4fc6a241b6df05fee901ce31a3a51091df1a2a98f053bf7ab3d302110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0a3d2afa502818d6bcc90fe0f6ba5b8599a693c1b5fe6d20e96391c5c82f263 0.600000000000 1425211 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": 965470, "vin": [ { "gen": { "height": 965460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0a3d2afa502818d6bcc90fe0f6ba5b8599a693c1b5fe6d20e96391c5c82f263" } } ], "extra": [ 1, 252, 126, 91, 103, 217, 58, 79, 198, 162, 65, 182, 223, 5, 254, 233, 1, 206, 49, 163, 165, 16, 145, 223, 26, 42, 152, 240, 83, 191, 122, 179, 211, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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