Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f3d551ae8e2dc3aafeb4c0efd8a6ffd8645177ef1c8387ca8551f81e2c3a3ca

Tx prefix hash: fa8fdfed12b4bd37cea018ebe1de7011445d1e9cbebae49b297d6dbc36af47d2
Tx public key: abb8a274f4aec3ff6da3151770e69d22b73ad55e86b2bb8ae58a4e886420359e
Timestamp: 1731193881 Timestamp [UCT]: 2024-11-09 23:11:21 Age [y:d:h:m:s]: 00:014:15:00:50
Block: 1150280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10458 RingCT/type: yes/0
Extra: 01abb8a274f4aec3ff6da3151770e69d22b73ad55e86b2bb8ae58a4e886420359e021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbb937e3e70d19343bea464f05310f23d6d43fd1c293b4a86f98d408bb4ffbed 0.600000000000 1635541 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": 1150290, "vin": [ { "gen": { "height": 1150280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbb937e3e70d19343bea464f05310f23d6d43fd1c293b4a86f98d408bb4ffbed" } } ], "extra": [ 1, 171, 184, 162, 116, 244, 174, 195, 255, 109, 163, 21, 23, 112, 230, 157, 34, 183, 58, 213, 94, 134, 178, 187, 138, 229, 138, 78, 136, 100, 32, 53, 158, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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