Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbcefc182dfe5180f54169a4dbb8686fe09fcc0a81324fb1d0edfba52154912d

Tx prefix hash: aefc3873ebb3b6e88b58babcb3b4031e2550e8b22b9e276d2ca770fbbe2141c4
Tx public key: b19dd5cd2d3dda3cf264f41d5fdad43f85dfe842011d59b2f765b2b653e5e167
Timestamp: 1743481167 Timestamp [UTC]: 2025-04-01 04:19:27 Age [y:d:h:m:s]: 01:044:06:56:08
Block: 1251729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282604 RingCT/type: yes/0
Extra: 01b19dd5cd2d3dda3cf264f41d5fdad43f85dfe842011d59b2f765b2b653e5e167021100000005a2ed016b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 52c5e419708677229b0795d2850a727e803053c7c7599d755d9f485b3c4ea2b7 0.000600000000 1738798 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": 1251739, "vin": [ { "gen": { "height": 1251729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52c5e419708677229b0795d2850a727e803053c7c7599d755d9f485b3c4ea2b7" } } ], "extra": [ 1, 177, 157, 213, 205, 45, 61, 218, 60, 242, 100, 244, 29, 95, 218, 212, 63, 133, 223, 232, 66, 1, 29, 89, 178, 247, 101, 178, 182, 83, 229, 225, 103, 2, 17, 0, 0, 0, 5, 162, 237, 1, 107, 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: