Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfff17087a2d7949812dc9713ea327f587c1d6401358f3d6201b238d623a7339

Tx prefix hash: 18a63c8c43c154a1d4c86ff6bae3ebfdc107ee70fc91c593193847e1b69e9e10
Tx public key: 12bef9e747ced07e582ae40e0d96fc3ecf323f5d6edc3e458ec899f9a8871b13
Timestamp: 1742783406 Timestamp [UTC]: 2025-03-24 02:30:06 Age [y:d:h:m:s]: 01:241:17:08:46
Block: 1245950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436952 RingCT/type: yes/0
Extra: 0112bef9e747ced07e582ae40e0d96fc3ecf323f5d6edc3e458ec899f9a8871b1302110000000224ff4ea1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3ea993cee57f0d4cea39b7b659556dcbdd7fb564ee8cb2b84323e53eb363478a 0.000600000000 1732945 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": 1245960, "vin": [ { "gen": { "height": 1245950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ea993cee57f0d4cea39b7b659556dcbdd7fb564ee8cb2b84323e53eb363478a" } } ], "extra": [ 1, 18, 190, 249, 231, 71, 206, 208, 126, 88, 42, 228, 14, 13, 150, 252, 62, 207, 50, 63, 93, 110, 220, 62, 69, 142, 200, 153, 249, 168, 135, 27, 19, 2, 17, 0, 0, 0, 2, 36, 255, 78, 161, 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: