Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48dca5100b7d1c91146d7fd1736aa20398b6b02b4b3234e2c76ec9398ff9ce70

Tx prefix hash: 47f9427aa5de457ff0127c787345edc15328b36b19abf1c2bfa0ecb7e039ff29
Tx public key: 311809b44274313c317cfb6e704237062c3849c4caa70171e2c59f15d8923b9d
Timestamp: 1754467656 Timestamp [UCT]: 2025-08-06 08:07:36 Age [y:d:h:m:s]: 00:018:11:48:38
Block: 1341347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12290 RingCT/type: yes/0
Extra: 01311809b44274313c317cfb6e704237062c3849c4caa70171e2c59f15d8923b9d021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae28f6270931b233924a7ba40b09d3a2cb0f911395d250fe47bb56251cedc2a6 0.600000000000 1829172 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": 1341357, "vin": [ { "gen": { "height": 1341347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae28f6270931b233924a7ba40b09d3a2cb0f911395d250fe47bb56251cedc2a6" } } ], "extra": [ 1, 49, 24, 9, 180, 66, 116, 49, 60, 49, 124, 251, 110, 112, 66, 55, 6, 44, 56, 73, 196, 202, 167, 1, 113, 226, 197, 159, 21, 216, 146, 59, 157, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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