Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35985fd09d90d041c35ee9552afcb03ee77cae900487fecb639920368c805a06

Tx prefix hash: c747b95958afb92b8dd0230ab4da8a6a68eb454cf6543991e0fc6d04b18d26d6
Tx public key: 56455e480d8d5c57e769675357f4bea74399e946a4b4b8f70ce2666cbbcd5112
Timestamp: 1736815890 Timestamp [UCT]: 2025-01-14 00:51:30 Age [y:d:h:m:s]: 00:058:12:56:25
Block: 1196824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41622 RingCT/type: yes/0
Extra: 0156455e480d8d5c57e769675357f4bea74399e946a4b4b8f70ce2666cbbcd51120211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 697d4d7ad8d99a175afc1cb6a03b7e826cfe4aafbe4992ed81852c37caf3f299 0.600000000000 1683427 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": 1196834, "vin": [ { "gen": { "height": 1196824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "697d4d7ad8d99a175afc1cb6a03b7e826cfe4aafbe4992ed81852c37caf3f299" } } ], "extra": [ 1, 86, 69, 94, 72, 13, 141, 92, 87, 231, 105, 103, 83, 87, 244, 190, 167, 67, 153, 233, 70, 164, 180, 184, 247, 12, 226, 102, 108, 187, 205, 81, 18, 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