Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc0485f06991b7c45d30b9e0fa197a835700324b7dd93bc1d3a627ff698ac29d

Tx prefix hash: 73b86ec70698f31493e8c2a1bdb14db07f3246882d438a60d02ab4677e8f37d0
Tx public key: d850c29ae69098898df79665351a2b87618c751edcf7d9408b7e3a47443a37d6
Timestamp: 1729532466 Timestamp [UCT]: 2024-10-21 17:41:06 Age [y:d:h:m:s]: 00:240:06:13:05
Block: 1136548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171428 RingCT/type: yes/0
Extra: 01d850c29ae69098898df79665351a2b87618c751edcf7d9408b7e3a47443a37d6021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 111ade6f9373a0c1c340fde2f3ac62c8cb3c01f1a3fed659bda28ea564e86ae7 0.600000000000 1619895 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": 1136558, "vin": [ { "gen": { "height": 1136548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "111ade6f9373a0c1c340fde2f3ac62c8cb3c01f1a3fed659bda28ea564e86ae7" } } ], "extra": [ 1, 216, 80, 194, 154, 230, 144, 152, 137, 141, 247, 150, 101, 53, 26, 43, 135, 97, 140, 117, 30, 220, 247, 217, 64, 139, 126, 58, 71, 68, 58, 55, 214, 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