Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 789756fcef2eaffa9c9aef0e93967fb7b94494fa0ceb6ce3ecf5fb67844fe33f

Tx prefix hash: c704368acc563f4ed81b7e9d0b8c8bfd02bc0963dfa89c4130b8e87240477606
Tx public key: 17a2cb20d13a1965d0fd13415a1d5b9146331c871ca51712d03acbac14264d25
Timestamp: 1706392417 Timestamp [UCT]: 2024-01-27 21:53:37 Age [y:d:h:m:s]: 01:072:20:35:30
Block: 944708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313167 RingCT/type: yes/0
Extra: 0117a2cb20d13a1965d0fd13415a1d5b9146331c871ca51712d03acbac14264d2502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92ab39fc03bb46c8e88384a3f76a762bdafeb6afc92e9e0b322f0bf6016f5500 0.600000000000 1402994 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": 944718, "vin": [ { "gen": { "height": 944708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92ab39fc03bb46c8e88384a3f76a762bdafeb6afc92e9e0b322f0bf6016f5500" } } ], "extra": [ 1, 23, 162, 203, 32, 209, 58, 25, 101, 208, 253, 19, 65, 90, 29, 91, 145, 70, 51, 28, 135, 28, 165, 23, 18, 208, 58, 203, 172, 20, 38, 77, 37, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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