Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7a821dc524c6a1162ee9f98b7c14699377734efdbea73680b83ccdff470c22b

Tx prefix hash: 7d80f4097f0034e97f4fff85350a5319c7b0e952f68241c2368aa8084646c5fb
Tx public key: de35e435b82ce30b661edc6ce01644ee0a43fe33a088c8d392f0817a5aaecfa4
Timestamp: 1705800930 Timestamp [UCT]: 2024-01-21 01:35:30 Age [y:d:h:m:s]: 01:077:00:04:53
Block: 939799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316136 RingCT/type: yes/0
Extra: 01de35e435b82ce30b661edc6ce01644ee0a43fe33a088c8d392f0817a5aaecfa402110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d98f50bb668599ffbb7c596e83f7a10beeb6df98c94ef3bd8310b37d1aa1b97 0.600000000000 1397931 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": 939809, "vin": [ { "gen": { "height": 939799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d98f50bb668599ffbb7c596e83f7a10beeb6df98c94ef3bd8310b37d1aa1b97" } } ], "extra": [ 1, 222, 53, 228, 53, 184, 44, 227, 11, 102, 30, 220, 108, 224, 22, 68, 238, 10, 67, 254, 51, 160, 136, 200, 211, 146, 240, 129, 122, 90, 174, 207, 164, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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