Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ddda1865322a2d3f582381586c26cfe76c53facc8c38bc048e18bfa2c093f5a

Tx prefix hash: 0be21d4d07c3dedf2ade1d79499c63b6130984351f14c73d001ae3ea3bf25b1a
Tx public key: 50b45c4bafd4658aa79dfa6745bfd3941c620d9f1b0cdc479b241361b9253cb0
Timestamp: 1739958845 Timestamp [UTC]: 2025-02-19 09:54:05 Age [y:d:h:m:s]: 01:274:03:11:12
Block: 1222547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460163 RingCT/type: yes/0
Extra: 0150b45c4bafd4658aa79dfa6745bfd3941c620d9f1b0cdc479b241361b9253cb00211000000051f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bcb655931f027f57976054f5e219d59e7a9a37d3f1a81f27d3ea0be4fe8be9a8 0.000600000000 1709398 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 dinastycoin-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": 1222557, "vin": [ { "gen": { "height": 1222547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcb655931f027f57976054f5e219d59e7a9a37d3f1a81f27d3ea0be4fe8be9a8" } } ], "extra": [ 1, 80, 180, 92, 75, 175, 212, 101, 138, 167, 157, 250, 103, 69, 191, 211, 148, 28, 98, 13, 159, 27, 12, 220, 71, 155, 36, 19, 97, 185, 37, 60, 176, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: