Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffb906d79422d8b554ae89884592fe74b7c9e069cc5216424ff3bcd25635b7d4

Tx prefix hash: cf4010fc0c814e9206a64916d8b64a786892ca43e6caf20b58bb10013b37cf01
Tx public key: 6fe30ba39bffd66984b6411ed73b5cbc990c1b0620b373f44b72f9300bf36813
Timestamp: 1746424976 Timestamp [UTC]: 2025-05-05 06:02:56 Age [y:d:h:m:s]: 01:011:15:20:06
Block: 1276103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259273 RingCT/type: yes/0
Extra: 016fe30ba39bffd66984b6411ed73b5cbc990c1b0620b373f44b72f9300bf368130211000000019f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1fbbda9184204b05fde5a01cb9df56dc5468eef6f2a42870bb0a057c0d045ede 0.000600000000 1763426 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": 1276113, "vin": [ { "gen": { "height": 1276103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fbbda9184204b05fde5a01cb9df56dc5468eef6f2a42870bb0a057c0d045ede" } } ], "extra": [ 1, 111, 227, 11, 163, 155, 255, 214, 105, 132, 182, 65, 30, 215, 59, 92, 188, 153, 12, 27, 6, 32, 179, 115, 244, 75, 114, 249, 48, 11, 243, 104, 19, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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: