Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80622e21794df39f157c9330c39a34f5fd105c6cdb568c01d7d55898d8d12d16

Tx prefix hash: 986fa78784d623177867373852d27df058c1611419e34b874e4ce94d101349ce
Tx public key: 2ebb7b33a0fd8abd94816c96dfc0cfdf01f64e4545d89c5c624ed8f8d3c40122
Timestamp: 1735921755 Timestamp [UCT]: 2025-01-03 16:29:15 Age [y:d:h:m:s]: 00:166:07:21:58
Block: 1189432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118544 RingCT/type: yes/0
Extra: 012ebb7b33a0fd8abd94816c96dfc0cfdf01f64e4545d89c5c624ed8f8d3c40122021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d714458ae858798eb2eb1a625fde3105404e3cd5154e9e8d8b323772bdff2663 0.600000000000 1675941 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": 1189442, "vin": [ { "gen": { "height": 1189432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d714458ae858798eb2eb1a625fde3105404e3cd5154e9e8d8b323772bdff2663" } } ], "extra": [ 1, 46, 187, 123, 51, 160, 253, 138, 189, 148, 129, 108, 150, 223, 192, 207, 223, 1, 246, 78, 69, 69, 216, 156, 92, 98, 78, 216, 248, 211, 196, 1, 34, 2, 17, 0, 0, 0, 1, 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