Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26e762dc1aa739a7bf99bfae0149df512fce4b050da280107d50272d88a4718e

Tx prefix hash: 09b668f719cd4f1832919a24892e83f3bc6921454bcaaa495e2431aed1e77068
Tx public key: bd8bc2ec8ea2a5377976178a96af7abd0d3c1e49321dfd4a99a3a7511461d318
Timestamp: 1731483318 Timestamp [UCT]: 2024-11-13 07:35:18 Age [y:d:h:m:s]: 00:145:03:42:21
Block: 1152659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103570 RingCT/type: yes/0
Extra: 01bd8bc2ec8ea2a5377976178a96af7abd0d3c1e49321dfd4a99a3a7511461d3180211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c73ea8c0e38947dddb9795d61780c5e5749a1cbd429988ebe6dbe917b46288f 0.600000000000 1638262 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": 1152669, "vin": [ { "gen": { "height": 1152659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c73ea8c0e38947dddb9795d61780c5e5749a1cbd429988ebe6dbe917b46288f" } } ], "extra": [ 1, 189, 139, 194, 236, 142, 162, 165, 55, 121, 118, 23, 138, 150, 175, 122, 189, 13, 60, 30, 73, 50, 29, 253, 74, 153, 163, 167, 81, 20, 97, 211, 24, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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