Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6761ebe8a323098ddcbaa81c879fbc1f57da41d9556747e0c5b1df37875257c5

Tx prefix hash: dfb6259ea7fd7d5933c2836be293492ce7b5d72b0fe2a7b971eaeb6617b8bcd5
Tx public key: cfed828701b3ba6bc72173bb3bda989d992b4131671feb21dfa7cf29ed05e1c5
Timestamp: 1709129947 Timestamp [UCT]: 2024-02-28 14:19:07 Age [y:d:h:m:s]: 01:100:23:42:10
Block: 967440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333238 RingCT/type: yes/0
Extra: 01cfed828701b3ba6bc72173bb3bda989d992b4131671feb21dfa7cf29ed05e1c502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d3babf78f7c874f995350bee11f0375602fdc24d5ce71c951cadfb4eb5a2ef5 0.600000000000 1427219 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": 967450, "vin": [ { "gen": { "height": 967440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d3babf78f7c874f995350bee11f0375602fdc24d5ce71c951cadfb4eb5a2ef5" } } ], "extra": [ 1, 207, 237, 130, 135, 1, 179, 186, 107, 199, 33, 115, 187, 59, 218, 152, 157, 153, 43, 65, 49, 103, 31, 235, 33, 223, 167, 207, 41, 237, 5, 225, 197, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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