Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5c9e27fc8b7e7748febbba86330bfbd62615659e6768607c9a5689fbd305758

Tx prefix hash: 35a7bd9f60e530bf189e49f2c914ed807d13f8fd4accac4d082a156dc5c19467
Tx public key: 0cd31817f0b0c523d3910861fa2eea39311adc6794e9dec92e1edc9570a2d9a9
Timestamp: 1696698228 Timestamp [UCT]: 2023-10-07 17:03:48 Age [y:d:h:m:s]: 01:163:18:27:54
Block: 864572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378100 RingCT/type: yes/0
Extra: 010cd31817f0b0c523d3910861fa2eea39311adc6794e9dec92e1edc9570a2d9a902110000000275e3f0e9000000000000000000

1 output(s) for total of 0.838135234000 dcy

stealth address amount amount idx
00: a17cc9415a039ed5b515d603121ffc1d650f4c0e377af875cdc8711f056c1e4d 0.838135234000 1319092 of 0

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": 864582, "vin": [ { "gen": { "height": 864572 } } ], "vout": [ { "amount": 838135234, "target": { "key": "a17cc9415a039ed5b515d603121ffc1d650f4c0e377af875cdc8711f056c1e4d" } } ], "extra": [ 1, 12, 211, 24, 23, 240, 176, 197, 35, 211, 145, 8, 97, 250, 46, 234, 57, 49, 26, 220, 103, 148, 233, 222, 201, 46, 30, 220, 149, 112, 162, 217, 169, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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