Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc7a49658d9b41c6288e8f01161ad5baddc204e95aec439e01336f1942951e81

Tx prefix hash: bf0780327b49b71f470cc8971ebedeb0b480efa8930f329ba7ea7c5adeac7688
Tx public key: fb915e8ff209d68eb07326d33b52b3da132d9427fa2ce35b5157c7b2d80e43d2
Timestamp: 1713770871 Timestamp [UCT]: 2024-04-22 07:27:51 Age [y:d:h:m:s]: 00:247:21:41:56
Block: 1005910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177463 RingCT/type: yes/0
Extra: 01fb915e8ff209d68eb07326d33b52b3da132d9427fa2ce35b5157c7b2d80e43d2021100000003bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 428e1a00cbb0f2507cf0af8a9eafcca9a51e4205d527037d03ed31c6bd6aa9f8 0.600000000000 1466760 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": 1005920, "vin": [ { "gen": { "height": 1005910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "428e1a00cbb0f2507cf0af8a9eafcca9a51e4205d527037d03ed31c6bd6aa9f8" } } ], "extra": [ 1, 251, 145, 94, 143, 242, 9, 214, 142, 176, 115, 38, 211, 59, 82, 179, 218, 19, 45, 148, 39, 250, 44, 227, 91, 81, 87, 199, 178, 216, 14, 67, 210, 2, 17, 0, 0, 0, 3, 191, 162, 34, 33, 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