Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95fb9f2c0d6c3589d9235154030ce7818f4a73cd5800026e3730331d7b44f16f

Tx prefix hash: 75cab0398e4270fa0e33ff4ccfb3fe97e2af94296d88527f45920950d0c2dc0a
Tx public key: 1c64943391b172d7aac7e6397ef108b1b4ec8ac3c076f569d3b25d0a274ba4b2
Timestamp: 1707411211 Timestamp [UCT]: 2024-02-08 16:53:31 Age [y:d:h:m:s]: 01:068:11:54:24
Block: 953176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310021 RingCT/type: yes/0
Extra: 011c64943391b172d7aac7e6397ef108b1b4ec8ac3c076f569d3b25d0a274ba4b202110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fac5deb301e20961beaf2be220182dd03df2888859ea4fbfae97d8572ce89ad4 0.600000000000 1412350 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": 953186, "vin": [ { "gen": { "height": 953176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fac5deb301e20961beaf2be220182dd03df2888859ea4fbfae97d8572ce89ad4" } } ], "extra": [ 1, 28, 100, 148, 51, 145, 177, 114, 215, 170, 199, 230, 57, 126, 241, 8, 177, 180, 236, 138, 195, 192, 118, 245, 105, 211, 178, 93, 10, 39, 75, 164, 178, 2, 17, 0, 0, 0, 5, 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