Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 477aab7b7ab394177c264798cfebdb3ba33f9496b30c3025b756ede243bb8cd8

Tx prefix hash: a2e8dc723abf51e673427a842b6cdcc97bca3d3ca0433c01034ef79a2ef3eb1b
Tx public key: c94ae8106cb7b0ee59955cf46c9ab3a43cec83c2579a4a437624fb56e2299b9a
Timestamp: 1719404584 Timestamp [UCT]: 2024-06-26 12:23:04 Age [y:d:h:m:s]: 01:134:10:42:02
Block: 1052613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354637 RingCT/type: yes/0
Extra: 01c94ae8106cb7b0ee59955cf46c9ab3a43cec83c2579a4a437624fb56e2299b9a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fa80e1d85093c1d6bbadb1bbb98e842dacdf7ab96698e940ae5e60d3d725424 0.600000000000 1522944 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": 1052623, "vin": [ { "gen": { "height": 1052613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fa80e1d85093c1d6bbadb1bbb98e842dacdf7ab96698e940ae5e60d3d725424" } } ], "extra": [ 1, 201, 74, 232, 16, 108, 183, 176, 238, 89, 149, 92, 244, 108, 154, 179, 164, 60, 236, 131, 194, 87, 154, 74, 67, 118, 36, 251, 86, 226, 41, 155, 154, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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