Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 453638f5300561b8a99bb7434c445a10029f5f10c4d8c959338c74a40968e3d1

Tx prefix hash: d6b5cc1c8c7b34ca944f7e86b6ea850288105455157b450fcc1db8687d913d78
Tx public key: e653d7c50a8497517911b09aad20eeb61aa3d4ddacb575a73d95505c2ee18c03
Timestamp: 1730609878 Timestamp [UCT]: 2024-11-03 04:57:58 Age [y:d:h:m:s]: 00:155:00:44:48
Block: 1145431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110620 RingCT/type: yes/0
Extra: 01e653d7c50a8497517911b09aad20eeb61aa3d4ddacb575a73d95505c2ee18c030211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac9f2c913b83d02e43a42b5de0a11fa1458fbc034cb711ba2ae4e5f0995d6415 0.600000000000 1629862 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": 1145441, "vin": [ { "gen": { "height": 1145431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac9f2c913b83d02e43a42b5de0a11fa1458fbc034cb711ba2ae4e5f0995d6415" } } ], "extra": [ 1, 230, 83, 215, 197, 10, 132, 151, 81, 121, 17, 176, 154, 173, 32, 238, 182, 26, 163, 212, 221, 172, 181, 117, 167, 61, 149, 80, 92, 46, 225, 140, 3, 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