Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 508ee6d21ff5e299b7f54f53ed9ea5f79760ec57c9b2f5c0fa49eb10be030dcf

Tx prefix hash: 3c73455c188cdb2785aac2280d2d4026eee603a58a0a09aa6001115a82de34a5
Tx public key: 5bf06fc98e1bc82b5e640ea4ebb27a08c55a45227b7fa53eb0570cddd0f6eb4f
Timestamp: 1755056199 Timestamp [UCT]: 2025-08-13 03:36:39 Age [y:d:h:m:s]: 00:053:21:46:41
Block: 1345812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37869 RingCT/type: yes/0
Extra: 015bf06fc98e1bc82b5e640ea4ebb27a08c55a45227b7fa53eb0570cddd0f6eb4f021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a95d57bff5d3a44d6e82473da7b3825855e0a5abea2e52acc784dbe437520bc7 0.600000000000 1833707 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": 1345822, "vin": [ { "gen": { "height": 1345812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a95d57bff5d3a44d6e82473da7b3825855e0a5abea2e52acc784dbe437520bc7" } } ], "extra": [ 1, 91, 240, 111, 201, 142, 27, 200, 43, 94, 100, 14, 164, 235, 178, 122, 8, 197, 90, 69, 34, 123, 127, 165, 62, 176, 87, 12, 221, 208, 246, 235, 79, 2, 17, 0, 0, 0, 1, 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