Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcf07d31df845334105d36375b221c95f141a013cdfe335f77492aff9e2d29f1

Tx prefix hash: b4c6eee7f99a595c8b0f53cce2b69ab29904f5d4aa4b538aa6021803b8567a0c
Tx public key: 8c6a3ca68e0fac4b251569c42e90ea9af801046d10c2e4f64be6d5da6ebe24e5
Timestamp: 1794986957 Timestamp [UTC]: 2026-11-18 07:29:17 Age [y:d:h:m:s]: 00:001:14:54:06
Block: 1680975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 1229 RingCT/type: yes/0
Extra: 018c6a3ca68e0fac4b251569c42e90ea9af801046d10c2e4f64be6d5da6ebe24e5

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c44a8b5c2ddad29f5fa9767a8e1faa8f9cb3d470152cf6c0b57eed38cf81a3d9 0.000600000000 2171763 of 15 <84>

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": 1680985, "vin": [ { "gen": { "height": 1680975 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "c44a8b5c2ddad29f5fa9767a8e1faa8f9cb3d470152cf6c0b57eed38cf81a3d9", "view_tag": "84" } } } ], "extra": [ 1, 140, 106, 60, 166, 142, 15, 172, 75, 37, 21, 105, 196, 46, 144, 234, 154, 248, 1, 4, 109, 16, 194, 228, 246, 75, 230, 213, 218, 110, 190, 36, 229 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: