Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 212141969ee611f2a48b50822fcca8ef701bf0154f0e8a63c1853b7aea2df152

Tx prefix hash: f6d5492df70a3367fc3fc27d8ccecf63df489fad16cf1eea1bcec5ee8a64273f
Tx public key: 55e0f976829da15cfd4233027c4066f70ce0e5d0d6f310cf12f8e6e9b9e42219
Timestamp: 1712485042 Timestamp [UCT]: 2024-04-07 10:17:22 Age [y:d:h:m:s]: 01:069:08:29:02
Block: 995223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310495 RingCT/type: yes/0
Extra: 0155e0f976829da15cfd4233027c4066f70ce0e5d0d6f310cf12f8e6e9b9e422190211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cf8234b23f783fcb71dcdfebaf205f5153e414f38c2864c68ccea338251d061 0.600000000000 1455629 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": 995233, "vin": [ { "gen": { "height": 995223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cf8234b23f783fcb71dcdfebaf205f5153e414f38c2864c68ccea338251d061" } } ], "extra": [ 1, 85, 224, 249, 118, 130, 157, 161, 92, 253, 66, 51, 2, 124, 64, 102, 247, 12, 224, 229, 208, 214, 243, 16, 207, 18, 248, 230, 233, 185, 228, 34, 25, 2, 17, 0, 0, 0, 1, 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