Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf67674cfff104fe32097f4f3f338ae68f72b5557c5627b3d5cb37b322cdb516

Tx prefix hash: 0caa38f40e295f6bc703aebae3f65e55c4aef53e4e767104a34fb3fc468e3e2c
Tx public key: 4bc3ab601b28c96245cc8c803a64d6740ffcfac74a834696d037afc360c8b23d
Timestamp: 1737516735 Timestamp [UCT]: 2025-01-22 03:32:15 Age [y:d:h:m:s]: 00:150:00:01:22
Block: 1202586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106896 RingCT/type: yes/0
Extra: 014bc3ab601b28c96245cc8c803a64d6740ffcfac74a834696d037afc360c8b23d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e71119620765d6d3c167235f0c54eaf55bf5c9cba1daf985b6c243ccc660013 0.600000000000 1689251 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": 1202596, "vin": [ { "gen": { "height": 1202586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e71119620765d6d3c167235f0c54eaf55bf5c9cba1daf985b6c243ccc660013" } } ], "extra": [ 1, 75, 195, 171, 96, 27, 40, 201, 98, 69, 204, 140, 128, 58, 100, 214, 116, 15, 252, 250, 199, 74, 131, 70, 150, 208, 55, 175, 195, 96, 200, 178, 61, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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