Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd4999979707b2e2e2adb43aa3aaa190b32b7abd7dd4df9e8fc3ca769f0b8bc0

Tx prefix hash: 841a55dea7c68fd5bec0bc25d93539a0e900aaf2017d4723f54ca72355f3c00b
Tx public key: 0121a10210b58951a7a08b414ccba5934df6e36d56ee4e05ddc81df0db730bdf
Timestamp: 1768631635 Timestamp [UCT]: 2026-01-17 06:33:55 Age [y:d:h:m:s]: 00:009:01:36:20
Block: 1457453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6449 RingCT/type: yes/0
Extra: 010121a10210b58951a7a08b414ccba5934df6e36d56ee4e05ddc81df0db730bdf021100000003215bbf89000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 084ad25b065bee4c6317053bd2f4bc568de21e4055db6f483860b7b60d600c70 0.600000000000 1946581 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": 1457463, "vin": [ { "gen": { "height": 1457453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "084ad25b065bee4c6317053bd2f4bc568de21e4055db6f483860b7b60d600c70" } } ], "extra": [ 1, 1, 33, 161, 2, 16, 181, 137, 81, 167, 160, 139, 65, 76, 203, 165, 147, 77, 246, 227, 109, 86, 238, 78, 5, 221, 200, 29, 240, 219, 115, 11, 223, 2, 17, 0, 0, 0, 3, 33, 91, 191, 137, 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