Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1f5d2e5c26a497146f8ae190effc791b628b62de1f6505c49c75fa4fee0036e

Tx prefix hash: 48fbaf6ef9aaab7299e851c1c8daa1134c9e7a9107422a5439e7874064c55cd7
Tx public key: 43f8e08ce330ff40ad1ca258dfe2d2b667b6211b6ea8aa2875a1f50ed0e11cf2
Timestamp: 1753257953 Timestamp [UCT]: 2025-07-23 08:05:53 Age [y:d:h:m:s]: 00:117:06:38:45
Block: 1331516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82642 RingCT/type: yes/0
Extra: 0143f8e08ce330ff40ad1ca258dfe2d2b667b6211b6ea8aa2875a1f50ed0e11cf202110000000643846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79a5184499182473c93a1cea28d5d8450d9f4deb5967439d6cf21f40208b392a 0.600000000000 1819311 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": 1331526, "vin": [ { "gen": { "height": 1331516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79a5184499182473c93a1cea28d5d8450d9f4deb5967439d6cf21f40208b392a" } } ], "extra": [ 1, 67, 248, 224, 140, 227, 48, 255, 64, 173, 28, 162, 88, 223, 226, 210, 182, 103, 182, 33, 27, 110, 168, 170, 40, 117, 161, 245, 14, 208, 225, 28, 242, 2, 17, 0, 0, 0, 6, 67, 132, 109, 102, 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