Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67d1148ff6384eb73d921e6a3116c8e32b9684bfc5810235b0b7ac613b12eedf

Tx prefix hash: 8d3b6f73d1441648da3a75f89ed7fb5deb85e5f84c94cab29842de896ccec4b6
Tx public key: 5fce812f9241e11419dce35778aae136597e5e30df3cc18f0c32721ac24f03c8
Timestamp: 1729708140 Timestamp [UCT]: 2024-10-23 18:29:00 Age [y:d:h:m:s]: 00:141:04:07:43
Block: 1138004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100704 RingCT/type: yes/0
Extra: 015fce812f9241e11419dce35778aae136597e5e30df3cc18f0c32721ac24f03c80211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1425e860f6ed7785b9e85bebee78203982d7557a3dc1fac6010cc948780469a 0.600000000000 1621601 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": 1138014, "vin": [ { "gen": { "height": 1138004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1425e860f6ed7785b9e85bebee78203982d7557a3dc1fac6010cc948780469a" } } ], "extra": [ 1, 95, 206, 129, 47, 146, 65, 225, 20, 25, 220, 227, 87, 120, 170, 225, 54, 89, 126, 94, 48, 223, 60, 193, 143, 12, 50, 114, 26, 194, 79, 3, 200, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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