Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9b086e0353b4c98aee6c885f73f9c37cf7dd3b001c09127077cceb0f31dadb0

Tx prefix hash: f49ae81bb0169b8ef16ba725ff95fa4e168adfd5a2f4efa38e7d2b0843a138e1
Tx public key: 9ef5c727389c67850ce9917a846d47b87e7e6ab8b2e5a3cab9269ba9900ba670
Timestamp: 1747010870 Timestamp [UCT]: 2025-05-12 00:47:50 Age [y:d:h:m:s]: 00:239:01:19:23
Block: 1280952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168637 RingCT/type: yes/0
Extra: 019ef5c727389c67850ce9917a846d47b87e7e6ab8b2e5a3cab9269ba9900ba6700211000000069f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36368cb8a599cf22b294356bd31bdd394d8c9ae84c783204a13e5779f4e57cef 0.600000000000 1768345 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": 1280962, "vin": [ { "gen": { "height": 1280952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36368cb8a599cf22b294356bd31bdd394d8c9ae84c783204a13e5779f4e57cef" } } ], "extra": [ 1, 158, 245, 199, 39, 56, 156, 103, 133, 12, 233, 145, 122, 132, 109, 71, 184, 126, 126, 106, 184, 178, 229, 163, 202, 185, 38, 155, 169, 144, 11, 166, 112, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 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