Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 815a749f19bba9a96a242e395e0adf601894f2cf61a883989de534e2db1cb5d2

Tx prefix hash: 63e4e0f93b7796879eaae20a8cd15c6b21c5ae21559a5dfe7766383e999554e2
Tx public key: fe64d540c12613bdb33c3eccd598d1dd5e14340443dc9a002cf032997b995335
Timestamp: 1733994778 Timestamp [UCT]: 2024-12-12 09:12:58 Age [y:d:h:m:s]: 00:111:06:11:12
Block: 1173496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79286 RingCT/type: yes/0
Extra: 01fe64d540c12613bdb33c3eccd598d1dd5e14340443dc9a002cf032997b99533502110000000e007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f10f141031638d4cb15fa8b1c7083dfdc806a3cacd0c1e133f7dbe775e17c70f 0.600000000000 1659525 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": 1173506, "vin": [ { "gen": { "height": 1173496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f10f141031638d4cb15fa8b1c7083dfdc806a3cacd0c1e133f7dbe775e17c70f" } } ], "extra": [ 1, 254, 100, 213, 64, 193, 38, 19, 189, 179, 60, 62, 204, 213, 152, 209, 221, 94, 20, 52, 4, 67, 220, 154, 0, 44, 240, 50, 153, 123, 153, 83, 53, 2, 17, 0, 0, 0, 14, 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