Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 716f3836e4224f994221a23afacf84e4128ca8a0958486d477e0e9763993ee7c

Tx prefix hash: 66b106a2b4dd3096258b02c2eba3cb0c7057ed53d2a4d01431d033b8f6d71a3a
Tx public key: 60a1c841004da8f68802f85d243fad43eba50ec50aa3e37c4354c39f20be9f36
Timestamp: 1723626239 Timestamp [UCT]: 2024-08-14 09:03:59 Age [y:d:h:m:s]: 01:083:20:51:40
Block: 1087627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318385 RingCT/type: yes/0
Extra: 0160a1c841004da8f68802f85d243fad43eba50ec50aa3e37c4354c39f20be9f3602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c0467b338969bfe8ffe7f52096479d928a337d2f2ba9fa34d463f677b9f8828 0.600000000000 1562236 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": 1087637, "vin": [ { "gen": { "height": 1087627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c0467b338969bfe8ffe7f52096479d928a337d2f2ba9fa34d463f677b9f8828" } } ], "extra": [ 1, 96, 161, 200, 65, 0, 77, 168, 246, 136, 2, 248, 93, 36, 63, 173, 67, 235, 165, 14, 197, 10, 163, 227, 124, 67, 84, 195, 159, 32, 190, 159, 54, 2, 17, 0, 0, 0, 4, 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