Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fcb3aac64034a7419a03401d6a8075f891b2253914184fb9f9408a37bae777b

Tx prefix hash: a769af0d12574474b632509ce78b8c8bbacb94518305cf87fd7801e19c913777
Tx public key: 88a79302fb41bb0c25a8286f04481929a33ab9d8048557d252ef0901d59cf613
Timestamp: 1741138887 Timestamp [UTC]: 2025-03-05 01:41:27 Age [y:d:h:m:s]: 00:348:14:06:49
Block: 1232348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246791 RingCT/type: yes/0
Extra: 0188a79302fb41bb0c25a8286f04481929a33ab9d8048557d252ef0901d59cf6130211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8f2575270330e53997ff5481b4f1287a1592f4a45a77cbcc9d08e946c747e8f3 0.000600000000 1719261 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": 1232358, "vin": [ { "gen": { "height": 1232348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f2575270330e53997ff5481b4f1287a1592f4a45a77cbcc9d08e946c747e8f3" } } ], "extra": [ 1, 136, 167, 147, 2, 251, 65, 187, 12, 37, 168, 40, 111, 4, 72, 25, 41, 163, 58, 185, 216, 4, 133, 87, 210, 82, 239, 9, 1, 213, 156, 246, 19, 2, 17, 0, 0, 0, 2, 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) | dinastycoin version: tesla-369