Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0bbcfcb606be61e30c90f3392b34e34e5f000893bff8faf1f1ef65bf0ee583a

Tx prefix hash: 518ea46db8dfee975a43d5e0d15e4f7803f40c22414ff8b2088c8313fd8aeeaa
Tx public key: bac0878323ed1d6412f3b9438c1af93420cbe08e040cb5e5e1f42fd9e93aceab
Timestamp: 1687715699 Timestamp [UCT]: 2023-06-25 17:54:59 Age [y:d:h:m:s]: 01:246:03:04:30
Block: 790165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437027 RingCT/type: yes/0
Extra: 01bac0878323ed1d6412f3b9438c1af93420cbe08e040cb5e5e1f42fd9e93aceab0211000000234b8f5122000000000000000000

1 output(s) for total of 1.478616289000 dcy

stealth address amount amount idx
00: 9af84a525944d0ba9d027e959239f6423c7a9a2bbc977330c20a280aac1b8d62 1.478616289000 1240448 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": 790175, "vin": [ { "gen": { "height": 790165 } } ], "vout": [ { "amount": 1478616289, "target": { "key": "9af84a525944d0ba9d027e959239f6423c7a9a2bbc977330c20a280aac1b8d62" } } ], "extra": [ 1, 186, 192, 135, 131, 35, 237, 29, 100, 18, 243, 185, 67, 140, 26, 249, 52, 32, 203, 224, 142, 4, 12, 181, 229, 225, 244, 47, 217, 233, 58, 206, 171, 2, 17, 0, 0, 0, 35, 75, 143, 81, 34, 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