Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f80c7c3ec6ef857926e175f29cb73fefe89558c69ab9187033d5044ad0fdf51

Tx prefix hash: f80679c762abfb4924531404365ec2716918cbea734b23167c209e5a8c0dc700
Tx public key: 905cf669e37d08314fab364397a0d9743ba1cafd3d38e1017d6ce2d697c958ac
Timestamp: 1701641176 Timestamp [UCT]: 2023-12-03 22:06:16 Age [y:d:h:m:s]: 01:123:12:24:20
Block: 905349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349434 RingCT/type: yes/0
Extra: 01905cf669e37d08314fab364397a0d9743ba1cafd3d38e1017d6ce2d697c958ac0211000000014b8f5122000000000000000000

1 output(s) for total of 0.614048833000 dcy

stealth address amount amount idx
00: 8e16c26d34d71c89bbbf9506a6fb26e3e24787167a8ffb68d416b3b8c18f532a 0.614048833000 1362232 of 0

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": 905359, "vin": [ { "gen": { "height": 905349 } } ], "vout": [ { "amount": 614048833, "target": { "key": "8e16c26d34d71c89bbbf9506a6fb26e3e24787167a8ffb68d416b3b8c18f532a" } } ], "extra": [ 1, 144, 92, 246, 105, 227, 125, 8, 49, 79, 171, 54, 67, 151, 160, 217, 116, 59, 161, 202, 253, 61, 56, 225, 1, 125, 108, 226, 214, 151, 201, 88, 172, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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