Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9e97c3176aa09161eb0c736e748aa6ebddde93a86dcca8522e674cbe2332f5d

Tx prefix hash: c982e67cbfd6214baa0097deb6d2371b2e6c37251e11a357c51893867fbe0ad2
Tx public key: 6626736cfa2f141345e0a881cb7d1a99750a150507f41c7b631ae19fb0c311d9
Timestamp: 1739008500 Timestamp [UCT]: 2025-02-08 09:55:00 Age [y:d:h:m:s]: 00:353:16:16:07
Block: 1214712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250442 RingCT/type: yes/0
Extra: 016626736cfa2f141345e0a881cb7d1a99750a150507f41c7b631ae19fb0c311d9021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fed4ff3bfe6b4071747c871d55b63877077bf915f9657353a05ae50d38fbe63 0.600000000000 1701507 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": 1214722, "vin": [ { "gen": { "height": 1214712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fed4ff3bfe6b4071747c871d55b63877077bf915f9657353a05ae50d38fbe63" } } ], "extra": [ 1, 102, 38, 115, 108, 250, 47, 20, 19, 69, 224, 168, 129, 203, 125, 26, 153, 117, 10, 21, 5, 7, 244, 28, 123, 99, 26, 225, 159, 176, 195, 17, 217, 2, 17, 0, 0, 0, 4, 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