Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2b0efdc93f79a4a76f9e8d1c67d6a4a6b654bc69da54a73e6e935c544b17c41

Tx prefix hash: 9023cd2aaf325d92d784ff3c7e9412457c077b76682f98d8dba00d6bc6884bdb
Tx public key: f3afcb8d41e532bc7a1065a441b67793772dde7d572d07c7847ddefccda080f2
Timestamp: 1752105884 Timestamp [UCT]: 2025-07-10 00:04:44 Age [y:d:h:m:s]: 00:177:11:45:16
Block: 1322240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125492 RingCT/type: yes/0
Extra: 01f3afcb8d41e532bc7a1065a441b67793772dde7d572d07c7847ddefccda080f2021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94791a17040f140a507e135dda4e30d05ab4c1603e905bd7d32427f9e324c576 0.600000000000 1809967 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": 1322250, "vin": [ { "gen": { "height": 1322240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94791a17040f140a507e135dda4e30d05ab4c1603e905bd7d32427f9e324c576" } } ], "extra": [ 1, 243, 175, 203, 141, 65, 229, 50, 188, 122, 16, 101, 164, 65, 182, 119, 147, 119, 45, 222, 125, 87, 45, 7, 199, 132, 125, 222, 252, 205, 160, 128, 242, 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