Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c70feebd496c68d45cb2e276a9f0a67798c41a89b60a9103c0760b0e8b1c251

Tx prefix hash: dd716fdcca7adc831b35c52a41ca02fb2e3f5aa1e012819e7daeb7703af32dfb
Tx public key: bd9d3b6de94a74bb1ff00074a9954323d72d448ef0e401366e7c17eb21ca5580
Timestamp: 1765502054 Timestamp [UTC]: 2025-12-12 01:14:14 Age [y:d:h:m:s]: 00:340:19:03:31
Block: 1431655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248958 RingCT/type: yes/0
Extra: 01bd9d3b6de94a74bb1ff00074a9954323d72d448ef0e401366e7c17eb21ca5580021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a74d7b3928434f3f8ed2fc52c10da6d990ad06a089be0246496e09d1ba284bdb 0.000600000000 1920428 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": 1431665, "vin": [ { "gen": { "height": 1431655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a74d7b3928434f3f8ed2fc52c10da6d990ad06a089be0246496e09d1ba284bdb" } } ], "extra": [ 1, 189, 157, 59, 109, 233, 74, 116, 187, 31, 240, 0, 116, 169, 149, 67, 35, 215, 45, 68, 142, 240, 228, 1, 54, 110, 124, 23, 235, 33, 202, 85, 128, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 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: