Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7db7b219526be98c4f8c211c30baa7f55f15ebc579788d331441b62f51b02213

Tx prefix hash: 82c590d3b48588faf741b3834e28c5e42787e9b65d4fd648eb388232f8ce197e
Tx public key: 1df719740f7ed2bedacdbe8193f9d6f0225f3ab833e089b5a941d539383ed428
Timestamp: 1747326348 Timestamp [UCT]: 2025-05-15 16:25:48 Age [y:d:h:m:s]: 00:189:06:02:11
Block: 1283569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132961 RingCT/type: yes/0
Extra: 011df719740f7ed2bedacdbe8193f9d6f0225f3ab833e089b5a941d539383ed42802110000000a9f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7dd157aa90afdf45ac6f0d08dc78cfc16a9b0e113bc9254f53e7c536ce62d01 0.600000000000 1770988 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": 1283579, "vin": [ { "gen": { "height": 1283569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7dd157aa90afdf45ac6f0d08dc78cfc16a9b0e113bc9254f53e7c536ce62d01" } } ], "extra": [ 1, 29, 247, 25, 116, 15, 126, 210, 190, 218, 205, 190, 129, 147, 249, 214, 240, 34, 95, 58, 184, 51, 224, 137, 181, 169, 65, 213, 57, 56, 62, 212, 40, 2, 17, 0, 0, 0, 10, 159, 159, 230, 140, 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