Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1435c67a03845d73f8d21adc468b1737a3af843c7deadc359402b7c39e9b7661

Tx prefix hash: 532f044350b30d7ccf6983e9c50ed66d87fd0c54e8388ace9be7301dcd9cadb1
Tx public key: 53d2249bff1363165fd5e90121126e6bc1c2e1e20d4da9d8281e9f475a9d1a1d
Timestamp: 1684145843 Timestamp [UCT]: 2023-05-15 10:17:23 Age [y:d:h:m:s]: 01:364:23:24:24
Block: 760559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522100 RingCT/type: yes/0
Extra: 0153d2249bff1363165fd5e90121126e6bc1c2e1e20d4da9d8281e9f475a9d1a1d021100000002faf35c9c000000000000000000

1 output(s) for total of 1.853328898000 dcy

stealth address amount amount idx
00: df2ffa8d5159f2ba961f88cb890f78b1603583f73863f259400fbd8aff6307c0 1.853328898000 1209172 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": 760569, "vin": [ { "gen": { "height": 760559 } } ], "vout": [ { "amount": 1853328898, "target": { "key": "df2ffa8d5159f2ba961f88cb890f78b1603583f73863f259400fbd8aff6307c0" } } ], "extra": [ 1, 83, 210, 36, 155, 255, 19, 99, 22, 95, 213, 233, 1, 33, 18, 110, 107, 193, 194, 225, 226, 13, 77, 169, 216, 40, 30, 159, 71, 90, 157, 26, 29, 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