Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7580e63be9955c9bd418a8c6da1c6d9344ec4b5f9bccefa0db2c1785552d416b

Tx prefix hash: 524ad11c11b9ce9011ccba5aa6620ffe0be4d8f1628997cfed293c44825674e9
Tx public key: 35cbcc52eedf8130c8ece162251ce50c14d64617e51b6380c4fa4a1e9fe71e7e
Timestamp: 1734722422 Timestamp [UCT]: 2024-12-20 19:20:22 Age [y:d:h:m:s]: 00:292:01:26:35
Block: 1179518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206169 RingCT/type: yes/0
Extra: 0135cbcc52eedf8130c8ece162251ce50c14d64617e51b6380c4fa4a1e9fe71e7e0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5fc0edca915c457629bceee6f2c682a1abe7597a3cd06c26a223f8e159229a9 0.600000000000 1665913 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": 1179528, "vin": [ { "gen": { "height": 1179518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5fc0edca915c457629bceee6f2c682a1abe7597a3cd06c26a223f8e159229a9" } } ], "extra": [ 1, 53, 203, 204, 82, 238, 223, 129, 48, 200, 236, 225, 98, 37, 28, 229, 12, 20, 214, 70, 23, 229, 27, 99, 128, 196, 250, 74, 30, 159, 231, 30, 126, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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