Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a33b524d714519fba3cdddd7cca5c39bc5fc0870e1c64760609264e4db2d221b

Tx prefix hash: 30f9e3f73ca0373fd18fe8124ff850ce2e3afb0d290d49a3d644c295aacc7419
Tx public key: d175802a77308e67309832f5c1cf8d2d74d6028447c9cfb19271320bab3d7059
Timestamp: 1705652447 Timestamp [UCT]: 2024-01-19 08:20:47 Age [y:d:h:m:s]: 01:129:11:08:34
Block: 938586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353662 RingCT/type: yes/0
Extra: 01d175802a77308e67309832f5c1cf8d2d74d6028447c9cfb19271320bab3d705902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b884d7717d797c74c0b632b7685284c0bacecb5f614d9b4cc4d25ae324cf488 0.600000000000 1396656 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": 938596, "vin": [ { "gen": { "height": 938586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b884d7717d797c74c0b632b7685284c0bacecb5f614d9b4cc4d25ae324cf488" } } ], "extra": [ 1, 209, 117, 128, 42, 119, 48, 142, 103, 48, 152, 50, 245, 193, 207, 141, 45, 116, 214, 2, 132, 71, 201, 207, 177, 146, 113, 50, 11, 171, 61, 112, 89, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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