Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f52a9f42e35af97c68fd43b7f52951f97afaad838d78348535601d4e6c85ced

Tx prefix hash: 754675cf32f945054b261ce18b7a43e6ecb3ccd06494be2e10a925b96c1d1c6b
Tx public key: d0eb3a128d3c3a18a994557d5dfbb86bd97e5b44f1f51847933a888a4028e166
Timestamp: 1763151681 Timestamp [UCT]: 2025-11-14 20:21:21 Age [y:d:h:m:s]: 00:045:12:15:42
Block: 1412183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32587 RingCT/type: yes/0
Extra: 01d0eb3a128d3c3a18a994557d5dfbb86bd97e5b44f1f51847933a888a4028e16602110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cdd0eeac9a911e45a62c1fcfbcbd3c6f703799972d283db7bc4d33201644a56 0.600000000000 1900650 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": 1412193, "vin": [ { "gen": { "height": 1412183 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cdd0eeac9a911e45a62c1fcfbcbd3c6f703799972d283db7bc4d33201644a56" } } ], "extra": [ 1, 208, 235, 58, 18, 141, 60, 58, 24, 169, 148, 85, 125, 93, 251, 184, 107, 217, 126, 91, 68, 241, 245, 24, 71, 147, 58, 136, 138, 64, 40, 225, 102, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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