Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa50dcf6638c4fde61998d3be26d76b3f3179eaf4cf16cbc9a7f48a746a9843f

Tx prefix hash: f53b7a7abae9c847498deb022011c62d69e3b09103ce40b77acc727ab82b4c80
Tx public key: e4d909508e3389cfb861aa15c52ac920af60bfcb3280edc2e41cfda2a80b58dc
Timestamp: 1720910748 Timestamp [UCT]: 2024-07-13 22:45:48 Age [y:d:h:m:s]: 00:272:22:42:19
Block: 1065119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194987 RingCT/type: yes/0
Extra: 01e4d909508e3389cfb861aa15c52ac920af60bfcb3280edc2e41cfda2a80b58dc02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06c3ddfee656fd9647482f63f44e9d6735ada61d6cee9ab6fef9c980e36b14a4 0.600000000000 1535662 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": 1065129, "vin": [ { "gen": { "height": 1065119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06c3ddfee656fd9647482f63f44e9d6735ada61d6cee9ab6fef9c980e36b14a4" } } ], "extra": [ 1, 228, 217, 9, 80, 142, 51, 137, 207, 184, 97, 170, 21, 197, 42, 201, 32, 175, 96, 191, 203, 50, 128, 237, 194, 228, 28, 253, 162, 168, 11, 88, 220, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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