Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcde3c08d90c9a5b3993ed4dec8c7708daaa78ae81eed18774fb977bcccd8c75

Tx prefix hash: 0d7b7297026cda5df8eb2f12cf1cb689066408852308aa527077de2b9e3f0c64
Tx public key: 3c6a2923eff94f602556b50c983afc4058043964c9b3bd1a3a1b266e1934a620
Timestamp: 1696905040 Timestamp [UCT]: 2023-10-10 02:30:40 Age [y:d:h:m:s]: 02:026:12:20:03
Block: 866290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538565 RingCT/type: yes/0
Extra: 013c6a2923eff94f602556b50c983afc4058043964c9b3bd1a3a1b266e1934a620021100000002faf35c9c000000000000000000

1 output(s) for total of 0.827221186000 dcy

stealth address amount amount idx
00: 965427df19ecaf8cfd9dc3c003247a5b6d988c316d08fdca92a8373d7d638b1a 0.827221186000 1320870 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": 866300, "vin": [ { "gen": { "height": 866290 } } ], "vout": [ { "amount": 827221186, "target": { "key": "965427df19ecaf8cfd9dc3c003247a5b6d988c316d08fdca92a8373d7d638b1a" } } ], "extra": [ 1, 60, 106, 41, 35, 239, 249, 79, 96, 37, 86, 181, 12, 152, 58, 252, 64, 88, 4, 57, 100, 201, 179, 189, 26, 58, 27, 38, 110, 25, 52, 166, 32, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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