Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa1496510bb3a0b5fae2668d0c0c6b1ffc93e776ae3cfb70688fc1cb09c2346c

Tx prefix hash: 8121d149113cd2d4bb68386a077665fe6892bf182a3ed88c93d807624223ef5a
Tx public key: e32a146e3f2c61e474d908216cce773b32017924b7a47e3ae166148926fb5bee
Timestamp: 1733945208 Timestamp [UCT]: 2024-12-11 19:26:48 Age [y:d:h:m:s]: 00:111:05:48:06
Block: 1173083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79267 RingCT/type: yes/0
Extra: 01e32a146e3f2c61e474d908216cce773b32017924b7a47e3ae166148926fb5bee021100000001c7ca14c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 646fc8ba2d4d82e5e212caa0e13b2906d5e1662ac13f274d026d2632785c518a 0.600000000000 1659062 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": 1173093, "vin": [ { "gen": { "height": 1173083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "646fc8ba2d4d82e5e212caa0e13b2906d5e1662ac13f274d026d2632785c518a" } } ], "extra": [ 1, 227, 42, 20, 110, 63, 44, 97, 228, 116, 217, 8, 33, 108, 206, 119, 59, 50, 1, 121, 36, 183, 164, 126, 58, 225, 102, 20, 137, 38, 251, 91, 238, 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