Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 771778b0be234643b3cc5d4edc41f0dce2906e15fb1d4682f00c4d6c830d6412

Tx prefix hash: 326efca18c16dd623fa5e61fbb07b5e147ab0d2b8e1d459846750e01da27d628
Tx public key: 2735af3e8c4b537cc14583a46550af7e7ce75d7fd612099787aeb04709f3d3f4
Timestamp: 1706588937 Timestamp [UCT]: 2024-01-30 04:28:57 Age [y:d:h:m:s]: 01:283:22:20:46
Block: 946350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461720 RingCT/type: yes/0
Extra: 012735af3e8c4b537cc14583a46550af7e7ce75d7fd612099787aeb04709f3d3f40211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dbd07d46ba1bbc12d48da4aa5b00dd07d450e4074905e0c299b109a9c958582 0.600000000000 1404682 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": 946360, "vin": [ { "gen": { "height": 946350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dbd07d46ba1bbc12d48da4aa5b00dd07d450e4074905e0c299b109a9c958582" } } ], "extra": [ 1, 39, 53, 175, 62, 140, 75, 83, 124, 193, 69, 131, 164, 101, 80, 175, 126, 124, 231, 93, 127, 214, 18, 9, 151, 135, 174, 176, 71, 9, 243, 211, 244, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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