Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 936d6359b3e7f079f806cb27397897057d4561322840f0b47a71da8475e949d6

Tx prefix hash: 9b6da534734b353913350982f6241a849ce8352fc751db3ba95809c13555165a
Tx public key: c12e2926ca5c9d2a202aaac7a0fb1cb0aba48b6635dd06bd12fe36df7c04eadb
Timestamp: 1702821064 Timestamp [UCT]: 2023-12-17 13:51:04 Age [y:d:h:m:s]: 01:034:03:04:49
Block: 915127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285712 RingCT/type: yes/0
Extra: 01c12e2926ca5c9d2a202aaac7a0fb1cb0aba48b6635dd06bd12fe36df7c04eadb021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45e780aae5a82cfb4d645d478bf61f3cf88e454dea510914f060a96f5071d318 0.600000000000 1372513 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": 915137, "vin": [ { "gen": { "height": 915127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45e780aae5a82cfb4d645d478bf61f3cf88e454dea510914f060a96f5071d318" } } ], "extra": [ 1, 193, 46, 41, 38, 202, 92, 157, 42, 32, 42, 170, 199, 160, 251, 28, 176, 171, 164, 139, 102, 53, 221, 6, 189, 18, 254, 54, 223, 124, 4, 234, 219, 2, 17, 0, 0, 0, 1, 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