Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7436741e5af17cd556f5a8b9473beb5f44fa84d847068aaba51dd03b699df3f

Tx prefix hash: 4312e360531a9ab320757767e3abbe067f723f2d2353905e16895e58fea29078
Tx public key: db03c034d3b04254ac6dfa3501a65b6fdcfd4bbb64d2b5f2de888af8c50a9ad2
Timestamp: 1713676194 Timestamp [UCT]: 2024-04-21 05:09:54 Age [y:d:h:m:s]: 00:221:14:17:27
Block: 1005122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158638 RingCT/type: yes/0
Extra: 01db03c034d3b04254ac6dfa3501a65b6fdcfd4bbb64d2b5f2de888af8c50a9ad20211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f13dae2aba18d59e7290a4a358c4459b16d1ece431905390bd629e7a5817a44 0.600000000000 1465702 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": 1005132, "vin": [ { "gen": { "height": 1005122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f13dae2aba18d59e7290a4a358c4459b16d1ece431905390bd629e7a5817a44" } } ], "extra": [ 1, 219, 3, 192, 52, 211, 176, 66, 84, 172, 109, 250, 53, 1, 166, 91, 111, 220, 253, 75, 187, 100, 210, 181, 242, 222, 136, 138, 248, 197, 10, 154, 210, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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