Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cbfb916ca1af939104f9a84ee65fb3665ca2b5a17342ac9d853982c549a57b1

Tx prefix hash: c74f98981457d9da50edf78bf10ab5182d7615aeff90d25576b4e3ff2c75d355
Tx public key: 3d229e61e21eaa0ffd5d5e622bad90bef8303ee65cbbaaa164c1ee47cbcfd61d
Timestamp: 1713207150 Timestamp [UCT]: 2024-04-15 18:52:30 Age [y:d:h:m:s]: 00:357:00:14:25
Block: 1001223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255234 RingCT/type: yes/0
Extra: 013d229e61e21eaa0ffd5d5e622bad90bef8303ee65cbbaaa164c1ee47cbcfd61d0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 432749de744f47a8d3227a0c8ee89bb68e3ef9c343cc305e35cb578582e0ef49 0.600000000000 1461727 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": 1001233, "vin": [ { "gen": { "height": 1001223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "432749de744f47a8d3227a0c8ee89bb68e3ef9c343cc305e35cb578582e0ef49" } } ], "extra": [ 1, 61, 34, 158, 97, 226, 30, 170, 15, 253, 93, 94, 98, 43, 173, 144, 190, 248, 48, 62, 230, 92, 187, 170, 161, 100, 193, 238, 71, 203, 207, 214, 29, 2, 17, 0, 0, 0, 2, 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