Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6feccc509055cd9f97b78855facfb6f922fdd22093f8936176be357d989d3ca9

Tx prefix hash: f0f44f01f55c698895e88f5e4d98a5f342abca2584722ab8788d29b2ef4c688d
Tx public key: d8e737613cf942f1c10741cc30b325356363cc0d27242c477a8fcc7f713edc45
Timestamp: 1742644250 Timestamp [UTC]: 2025-03-22 11:50:50 Age [y:d:h:m:s]: 01:243:20:28:27
Block: 1244813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438467 RingCT/type: yes/0
Extra: 01d8e737613cf942f1c10741cc30b325356363cc0d27242c477a8fcc7f713edc45021100000007ca0c97f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4b6a4c4d30a741b9279f678d4300986e43a1323c44b7db255e93f08190380ecc 0.000600000000 1731804 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": 1244823, "vin": [ { "gen": { "height": 1244813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b6a4c4d30a741b9279f678d4300986e43a1323c44b7db255e93f08190380ecc" } } ], "extra": [ 1, 216, 231, 55, 97, 60, 249, 66, 241, 193, 7, 65, 204, 48, 179, 37, 53, 99, 99, 204, 13, 39, 36, 44, 71, 122, 143, 204, 127, 113, 62, 220, 69, 2, 17, 0, 0, 0, 7, 202, 12, 151, 245, 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: