Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a71546fbc8cebb9b312e01f46990bbdf3bcdec70c6c5baf5790f4124e152910a

Tx prefix hash: c9ec2caa19b8ef7229b733e52c248c78d7d340ccccf435ea7ff301af598251a0
Tx public key: 16ff52cd1511d30f285c2332f99cacf2a6f07d2e11041d63a1d6b9f6e2fe5c06
Timestamp: 1736803401 Timestamp [UCT]: 2025-01-13 21:23:21 Age [y:d:h:m:s]: 00:155:22:36:30
Block: 1196718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111145 RingCT/type: yes/0
Extra: 0116ff52cd1511d30f285c2332f99cacf2a6f07d2e11041d63a1d6b9f6e2fe5c060211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 660d92e8664ceddfdcdc8379ece12af5d37dffa12ba9a40ac203f6e823c7b67a 0.600000000000 1683321 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": 1196728, "vin": [ { "gen": { "height": 1196718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "660d92e8664ceddfdcdc8379ece12af5d37dffa12ba9a40ac203f6e823c7b67a" } } ], "extra": [ 1, 22, 255, 82, 205, 21, 17, 211, 15, 40, 92, 35, 50, 249, 156, 172, 242, 166, 240, 125, 46, 17, 4, 29, 99, 161, 214, 185, 246, 226, 254, 92, 6, 2, 17, 0, 0, 0, 5, 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