Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ea8e7d5111fa51c11aff946e5153893cd6be377f94aece6e21612128768dd14

Tx prefix hash: 86db85a714ceda9323f251fe4ec8cb21a562a3625c01e5e63fcb20e94de6cc9f
Tx public key: a0fa3b257ac7b565464977797df44e25bfdfc9af429e6c922e5e8240721b65e0
Timestamp: 1702227453 Timestamp [UCT]: 2023-12-10 16:57:33 Age [y:d:h:m:s]: 01:051:12:34:11
Block: 910207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297932 RingCT/type: yes/0
Extra: 01a0fa3b257ac7b565464977797df44e25bfdfc9af429e6c922e5e8240721b65e0021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25444631d1ab95ae7a617159dec614cdb45bcecf660c8cb56a708d6245d4df52 0.600000000000 1367352 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": 910217, "vin": [ { "gen": { "height": 910207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25444631d1ab95ae7a617159dec614cdb45bcecf660c8cb56a708d6245d4df52" } } ], "extra": [ 1, 160, 250, 59, 37, 122, 199, 181, 101, 70, 73, 119, 121, 125, 244, 78, 37, 191, 223, 201, 175, 66, 158, 108, 146, 46, 94, 130, 64, 114, 27, 101, 224, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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