Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c6260e9adc0f5fe530c815765e2724a634d401fab8354084279e3dd5a9d7f33

Tx prefix hash: 6f90bde94b0905123378898b711a3050103da58d8ec0545ede6d4e914ed75439
Tx public key: 72e01062b7f8a322f025a290e48e40b7f843616c96661185f31579b751dea9dd
Timestamp: 1750326808 Timestamp [UCT]: 2025-06-19 09:53:28 Age [y:d:h:m:s]: 00:154:18:24:36
Block: 1308269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108429 RingCT/type: yes/0
Extra: 0172e01062b7f8a322f025a290e48e40b7f843616c96661185f31579b751dea9dd021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c71d401472fb17b0e32107aa5d9906c7a0c659ea49434a20a376e552a8633bf 0.600000000000 1795882 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": 1308279, "vin": [ { "gen": { "height": 1308269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c71d401472fb17b0e32107aa5d9906c7a0c659ea49434a20a376e552a8633bf" } } ], "extra": [ 1, 114, 224, 16, 98, 183, 248, 163, 34, 240, 37, 162, 144, 228, 142, 64, 183, 248, 67, 97, 108, 150, 102, 17, 133, 243, 21, 121, 183, 81, 222, 169, 221, 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