Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 365487aa4da4e812e3cd8b44c707d7d72b085e45a3373869b7bd61cab31fa024

Tx prefix hash: 4c5269c7627eee80d70a544f79db1de583e8bb5f5bc2870dd7adbb336cb3b7bb
Tx public key: dfefe1403d98ce95929930b0e333c1c67015caff1b57a41f73c3e41faf4b27a5
Timestamp: 1737623697 Timestamp [UCT]: 2025-01-23 09:14:57 Age [y:d:h:m:s]: 00:296:09:44:02
Block: 1203466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209388 RingCT/type: yes/0
Extra: 01dfefe1403d98ce95929930b0e333c1c67015caff1b57a41f73c3e41faf4b27a50211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3524d1437fb535b5d38f85f7271561c9021e87f13eff3ecf109d912a6f69bee 0.600000000000 1690143 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": 1203476, "vin": [ { "gen": { "height": 1203466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3524d1437fb535b5d38f85f7271561c9021e87f13eff3ecf109d912a6f69bee" } } ], "extra": [ 1, 223, 239, 225, 64, 61, 152, 206, 149, 146, 153, 48, 176, 227, 51, 193, 198, 112, 21, 202, 255, 27, 87, 164, 31, 115, 195, 228, 31, 175, 75, 39, 165, 2, 17, 0, 0, 0, 8, 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