Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8944a01a4782a74d4ef2b49cdd40a6eb2dd203a31b4b81aef0c814a84cc98409

Tx prefix hash: d19cd22a55c4e5450b747889ded132cc4477e0c394b447371fe70d05ce097418
Tx public key: 7aeb959d1fe8f8caf1de8a5e523a57b2d489e9687068fe1fdec286f21a7ff42b
Timestamp: 1752710988 Timestamp [UCT]: 2025-07-17 00:09:48 Age [y:d:h:m:s]: 00:127:14:24:34
Block: 1327040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89968 RingCT/type: yes/0
Extra: 017aeb959d1fe8f8caf1de8a5e523a57b2d489e9687068fe1fdec286f21a7ff42b02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6036b307f1d3baf28052d8e9c7f39fe6bff305899a73ace9e474b4c65aac2d40 0.600000000000 1814793 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": 1327050, "vin": [ { "gen": { "height": 1327040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6036b307f1d3baf28052d8e9c7f39fe6bff305899a73ace9e474b4c65aac2d40" } } ], "extra": [ 1, 122, 235, 149, 157, 31, 232, 248, 202, 241, 222, 138, 94, 82, 58, 87, 178, 212, 137, 233, 104, 112, 104, 254, 31, 222, 194, 134, 242, 26, 127, 244, 43, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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