Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a484234659a89df3c0fc30ca27569304ee7f7e5094bd738cd262e2e5430d3db

Tx prefix hash: 3363709017873638e14c489107156d767a5f4c7b8d368371cfb5bec039e34df9
Tx public key: d48c7e39574c218fb9d0d2db97900bc76e6ff2e23427a74e13d73be90df24e1c
Timestamp: 1726661676 Timestamp [UCT]: 2024-09-18 12:14:36 Age [y:d:h:m:s]: 00:067:10:55:18
Block: 1112778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48224 RingCT/type: yes/0
Extra: 01d48c7e39574c218fb9d0d2db97900bc76e6ff2e23427a74e13d73be90df24e1c02110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b3506d99976e7aea708ace5d9d5eaea595e5ad814606182f01621bbd8a8db4a 0.600000000000 1592217 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": 1112788, "vin": [ { "gen": { "height": 1112778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b3506d99976e7aea708ace5d9d5eaea595e5ad814606182f01621bbd8a8db4a" } } ], "extra": [ 1, 212, 140, 126, 57, 87, 76, 33, 143, 185, 208, 210, 219, 151, 144, 11, 199, 110, 111, 242, 226, 52, 39, 167, 78, 19, 215, 59, 233, 13, 242, 78, 28, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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