Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f0ae35b39ed92ae9d4854a51ef90b7fa6a769f5255a1e79a4454966ccd51ff9

Tx prefix hash: c320a1550159b9a51e33e68a15c1b0fd5363a8c7c3758bebfbc7b4f42f1675e8
Tx public key: a1c1d0371ca398cabe1f6702eef87416062a294cfe246e501bd5aa952284db05
Timestamp: 1715765911 Timestamp [UCT]: 2024-05-15 09:38:31 Age [y:d:h:m:s]: 00:239:10:26:09
Block: 1022455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171363 RingCT/type: yes/0
Extra: 01a1c1d0371ca398cabe1f6702eef87416062a294cfe246e501bd5aa952284db0502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16cea72fb8ed151aa0db0414b0b69b863a707f47756322738dc3f281b73e47e8 0.600000000000 1487066 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": 1022465, "vin": [ { "gen": { "height": 1022455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16cea72fb8ed151aa0db0414b0b69b863a707f47756322738dc3f281b73e47e8" } } ], "extra": [ 1, 161, 193, 208, 55, 28, 163, 152, 202, 190, 31, 103, 2, 238, 248, 116, 22, 6, 42, 41, 76, 254, 36, 110, 80, 27, 213, 170, 149, 34, 132, 219, 5, 2, 17, 0, 0, 0, 1, 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