Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a119d3d75efe8b529b405c87744c6431dd7b58ba1e57bb63d335537018d080e5

Tx prefix hash: 69006272e5790ab45b058de8bebd5e6e3e85e1f63ab9a0069c729e17cee4e639
Tx public key: ed60f205452b82c2a2aa2d4e92b0d87f1d44337050ddbf4b1603748e035f88e1
Timestamp: 1735777907 Timestamp [UCT]: 2025-01-02 00:31:47 Age [y:d:h:m:s]: 00:119:01:28:13
Block: 1188226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84887 RingCT/type: yes/0
Extra: 01ed60f205452b82c2a2aa2d4e92b0d87f1d44337050ddbf4b1603748e035f88e1021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0796d6f117635a925d4cc9e2c6faad88a99db1630a1e72c15e624532d717e13 0.600000000000 1674727 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": 1188236, "vin": [ { "gen": { "height": 1188226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0796d6f117635a925d4cc9e2c6faad88a99db1630a1e72c15e624532d717e13" } } ], "extra": [ 1, 237, 96, 242, 5, 69, 43, 130, 194, 162, 170, 45, 78, 146, 176, 216, 127, 29, 68, 51, 112, 80, 221, 191, 75, 22, 3, 116, 142, 3, 95, 136, 225, 2, 17, 0, 0, 0, 2, 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