Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25242982ac177781acc0a1647e960f3039b6f44a1bd5a831d304045491655bb7

Tx prefix hash: c2201676b522f3e9584e82abc621651d2607a47100aa6f47529a2152ca4492f5
Tx public key: 641d98f63071e1d43192d4ee51b8c6b421197ec5e960af3bdd75860af996e5bf
Timestamp: 1673237242 Timestamp [UCT]: 2023-01-09 04:07:22 Age [y:d:h:m:s]: 02:143:09:03:51
Block: 670721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 624221 RingCT/type: yes/0
Extra: 01641d98f63071e1d43192d4ee51b8c6b421197ec5e960af3bdd75860af996e5bf02110000000152542ceb000000000000000000

1 output(s) for total of 3.678094250000 dcy

stealth address amount amount idx
00: ae11455b8dae2f5677ff0020cc47080b3b7c4280bf50e2c7331c36c88c7ead3e 3.678094250000 1112136 of 0

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": 670731, "vin": [ { "gen": { "height": 670721 } } ], "vout": [ { "amount": 3678094250, "target": { "key": "ae11455b8dae2f5677ff0020cc47080b3b7c4280bf50e2c7331c36c88c7ead3e" } } ], "extra": [ 1, 100, 29, 152, 246, 48, 113, 225, 212, 49, 146, 212, 238, 81, 184, 198, 180, 33, 25, 126, 197, 233, 96, 175, 59, 221, 117, 134, 10, 249, 150, 229, 191, 2, 17, 0, 0, 0, 1, 82, 84, 44, 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