Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed13c3e404b8945350854a6154a2a270be17a89f266d82e9e04de6b527db9c53

Tx prefix hash: ba74ed9625882761c47ca2648d21427b824fb8b945b86a6a3d597d1160c6c121
Tx public key: 4aa55bbfdce366e521d7597a9d7f58fac8726b4ce7e08f3c82e03fc137f16d96
Timestamp: 1711830014 Timestamp [UCT]: 2024-03-30 20:20:14 Age [y:d:h:m:s]: 00:335:23:18:24
Block: 989837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240173 RingCT/type: yes/0
Extra: 014aa55bbfdce366e521d7597a9d7f58fac8726b4ce7e08f3c82e03fc137f16d960211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e40c5b792c972eb13f1d3f783843dc187e60f9abb851e8539c142dfee67fcad 0.600000000000 1450155 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": 989847, "vin": [ { "gen": { "height": 989837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e40c5b792c972eb13f1d3f783843dc187e60f9abb851e8539c142dfee67fcad" } } ], "extra": [ 1, 74, 165, 91, 191, 220, 227, 102, 229, 33, 215, 89, 122, 157, 127, 88, 250, 200, 114, 107, 76, 231, 224, 143, 60, 130, 224, 63, 193, 55, 241, 109, 150, 2, 17, 0, 0, 0, 1, 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