Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5f2e6301751c7cdced191267a96a14d2252c2b8d2ce5d30bc6935ca2784d027

Tx prefix hash: bfd0b49215138f1eaedea88ac3f08632c5b83e5c56c796e44438a18effd6696c
Tx public key: 9c654721bd0eef45aaf7e8647bf0f58d810f81978f5342acc2a2d5e12cfa2feb
Timestamp: 1763839784 Timestamp [UTC]: 2025-11-22 19:29:44 Age [y:d:h:m:s]: 00:360:18:23:38
Block: 1417877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263295 RingCT/type: yes/0
Extra: 019c654721bd0eef45aaf7e8647bf0f58d810f81978f5342acc2a2d5e12cfa2feb02110000000170609d03000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2f6274a9bd970fbc3732327ddacc4e151b9e420f3e60ee0d36f4d33e33bffae3 0.000600000000 1906404 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": 1417887, "vin": [ { "gen": { "height": 1417877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f6274a9bd970fbc3732327ddacc4e151b9e420f3e60ee0d36f4d33e33bffae3" } } ], "extra": [ 1, 156, 101, 71, 33, 189, 14, 239, 69, 170, 247, 232, 100, 123, 240, 245, 141, 129, 15, 129, 151, 143, 83, 66, 172, 194, 162, 213, 225, 44, 250, 47, 235, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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: