Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8944d854745f15c16ff9c9cbaf233ddffbad50cb681d0a9e2ce167339078d9a6

Tx prefix hash: 6ea5e9f1167226b852c44318d5df6f4daa260cf92e725c6541886c2232a47e8e
Tx public key: 3f55eac967ca1a97d1418dd7df45d0d28177f036f8f7c059b2c7ce306ddf3ac4
Timestamp: 1737055753 Timestamp [UCT]: 2025-01-16 19:29:13 Age [y:d:h:m:s]: 00:153:01:56:54
Block: 1198804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109104 RingCT/type: yes/0
Extra: 013f55eac967ca1a97d1418dd7df45d0d28177f036f8f7c059b2c7ce306ddf3ac4021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96d2150639d415922582a0070bc979a906aa55c795d468002bc06ddbf9e3ff23 0.600000000000 1685431 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": 1198814, "vin": [ { "gen": { "height": 1198804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96d2150639d415922582a0070bc979a906aa55c795d468002bc06ddbf9e3ff23" } } ], "extra": [ 1, 63, 85, 234, 201, 103, 202, 26, 151, 209, 65, 141, 215, 223, 69, 208, 210, 129, 119, 240, 54, 248, 247, 192, 89, 178, 199, 206, 48, 109, 223, 58, 196, 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