Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfde75c5aa435307433b45db08840b7bd0eb076207422b42283bdccf70c5b376

Tx prefix hash: cd54ff5b786320e8beccbe32215be153794dba66ccfd44195e3f3e3444a7e0e0
Tx public key: 9d2998a86e95d468f453cb2378434fb07a87d856483255ce1a69b88db4fdb270
Timestamp: 1746230719 Timestamp [UTC]: 2025-05-03 00:05:19 Age [y:d:h:m:s]: 01:008:20:10:16
Block: 1274497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257041 RingCT/type: yes/0
Extra: 019d2998a86e95d468f453cb2378434fb07a87d856483255ce1a69b88db4fdb2700211000000011f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c1c41d4152028d76937c1d525202328c4eaa8f80ff0c9c4277f0ef67225f8245 0.000600000000 1761792 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": 1274507, "vin": [ { "gen": { "height": 1274497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1c41d4152028d76937c1d525202328c4eaa8f80ff0c9c4277f0ef67225f8245" } } ], "extra": [ 1, 157, 41, 152, 168, 110, 149, 212, 104, 244, 83, 203, 35, 120, 67, 79, 176, 122, 135, 216, 86, 72, 50, 85, 206, 26, 105, 184, 141, 180, 253, 178, 112, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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: