Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbf8fce3c38cd10a4804b63f62b976534dba46c57b172882c12a2f4dc1435681

Tx prefix hash: 0f64d4595f83c6e3e4f2b54243fd925d4a89c0cfa754a938d7c3eb8cf7d9ed27
Tx public key: 22708e2d0a6c4096ad873e4af713f1a0d281b3df8a3bb0900582bd856024f7c4
Timestamp: 1789568196 Timestamp [UTC]: 2026-09-16 14:16:36 Age [y:d:h:m:s]: 00:066:20:55:33
Block: 1636775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 46719 RingCT/type: yes/0
Extra: 0122708e2d0a6c4096ad873e4af713f1a0d281b3df8a3bb0900582bd856024f7c4

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 507890dbfebb828cec2ab1ef9e6f6ef281d2dc2fc36d7b32c0f2baf70afb49b7 0.000600000000 2126805 of 15 <c8>

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": 1636785, "vin": [ { "gen": { "height": 1636775 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "507890dbfebb828cec2ab1ef9e6f6ef281d2dc2fc36d7b32c0f2baf70afb49b7", "view_tag": "c8" } } } ], "extra": [ 1, 34, 112, 142, 45, 10, 108, 64, 150, 173, 135, 62, 74, 247, 19, 241, 160, 210, 129, 179, 223, 138, 59, 176, 144, 5, 130, 189, 133, 96, 36, 247, 196 ], "rct_signatures": { "type": 0 } }


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