Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c52d228f2278327b56e6b8baf92b6bc5720bdeb01d819dd3f06623abe4b415c

Tx prefix hash: d5cb8ac0aeba20af70995d87f334cb7d3e5e55de43583c6ac4a02a6a8105900c
Tx public key: aa1be1452424bcb4852681e37605f29de1bc03ec7f66e044d8f4657dc3ca56dd
Timestamp: 1733964035 Timestamp [UCT]: 2024-12-12 00:40:35 Age [y:d:h:m:s]: 00:110:23:40:29
Block: 1173238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79082 RingCT/type: yes/0
Extra: 01aa1be1452424bcb4852681e37605f29de1bc03ec7f66e044d8f4657dc3ca56dd021100000001c7ca14c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d45e02f984b9a47dcb5fba479c7265da43e458e536495d78b55a91c4cb589d5c 0.600000000000 1659237 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": 1173248, "vin": [ { "gen": { "height": 1173238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d45e02f984b9a47dcb5fba479c7265da43e458e536495d78b55a91c4cb589d5c" } } ], "extra": [ 1, 170, 27, 225, 69, 36, 36, 188, 180, 133, 38, 129, 227, 118, 5, 242, 157, 225, 188, 3, 236, 127, 102, 224, 68, 216, 244, 101, 125, 195, 202, 86, 221, 2, 17, 0, 0, 0, 1, 199, 202, 20, 193, 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