Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4243f504345768868a039a78f54939070b76ee109d89e9ca9907052baa2bc9ff

Tx prefix hash: cb231c202961a65513ff1825a45198718caea080bb9a7da90204c6ba2b9ff5dd
Tx public key: 95160076d149f1ee104bc97a9e95d2cc562e3e418c8b3fbb1a5ff8692b255015
Timestamp: 1730423407 Timestamp [UCT]: 2024-11-01 01:10:07 Age [y:d:h:m:s]: 00:147:21:52:32
Block: 1143895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105534 RingCT/type: yes/0
Extra: 0195160076d149f1ee104bc97a9e95d2cc562e3e418c8b3fbb1a5ff8692b255015021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2a306a71d7175cb2b2b7764ecc6f7a9c2c5d73fb7e664fcd7b35ed733612dba 0.600000000000 1627920 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": 1143905, "vin": [ { "gen": { "height": 1143895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2a306a71d7175cb2b2b7764ecc6f7a9c2c5d73fb7e664fcd7b35ed733612dba" } } ], "extra": [ 1, 149, 22, 0, 118, 209, 73, 241, 238, 16, 75, 201, 122, 158, 149, 210, 204, 86, 46, 62, 65, 140, 139, 63, 187, 26, 95, 248, 105, 43, 37, 80, 21, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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